All scored servers

Transit MCP: tool descriptions scored com.transitmcp/transit-mcp

tools/list taken
(UTC)
Connected to
https://transitmcp.com/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how Transit MCP (com.transitmcp/transit-mcp)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/com.transitmcp/transit-mcp
Average score
54.4 / 100Cloudy
Tools
18
Near-identical descriptions
0

Across the server

  • Minor
    The server's instructions are 2557 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools

get_elevator_incidents

29 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
8 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (9 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: city.param_no_description

get_incidents

40 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
8 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: city.param_no_description

get_route_info

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: city.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: routeId. Name the tool or the place that returns it, or models look it up first.id_source_missing

get_stations_by_line

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: city.param_no_description

search_stations

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: city.param_no_description

get_bus_positions

48 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    No `required` list, so every argument is optional.no_required

get_station_transfers

50 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: city.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: stationId. Name the tool or the place that returns it, or models look it up first.id_source_missing

get_bus_routes

53 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

get_train_positions

53 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

get_bus_predictions

56 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Required identifiers whose description does not say where the value comes from: stopId. Name the tool or the place that returns it, or models look it up first.id_source_missing

find_transit

57 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: context, context.feed, context.serviceDate, limit, longitude.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

get_bus_stops

59 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    No `required` list, so every argument is optional.no_required

get_station_predictions

60 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
13 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: city.param_no_description

get_all_stations

62 / 100Cloudy

Purpose
17 / 20
When to use
15 / 20
Arguments
8 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: city.param_no_description

get_service_status

62 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
22 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    No `required` list, so every argument is optional.no_required

get_vehicle_status

65 / 100Cloudy

Purpose
17 / 20
When to use
10 / 20
Arguments
18 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: limit.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

get_departures

67 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: at, routeRefs, agencyRefs, selection, limit.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

plan_trip

84 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
17 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Arguments without a description: origin, destination, departAt, windowSeconds, maxTransfers.param_no_description

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers