Skip to main content
Glama

DealLabs

Get station exits

get_station_exit
Read-only

The station record, its exits, its last-train times by line and direction (weekday, Saturday and Sunday; Seoul and Busan publish them; other cities answer last_trains as not_published), and (with "to") the walk from the station to a destination record. Takes the station name in common spellings (for example Myeong-dong, Hongik Univ., 명동역) or a place_id. Exit positions are OpenStreetMap data (ODbL 1.0).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>",
      "station": "<station>"
    },
    "name": "get_station_exit"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional place_id of the destination.
cityYesCity key, e.g. "seoul".
stationYesStation name or place_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint=true already covering the safety profile, the description adds useful behavioral context: last-train availability depends on city, with Seoul and Busan publishing and other cities returning last_trains as not_published. It also discloses that exit positions come from OpenStreetMap under ODbL 1.0, which is meaningful provenance beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded around "The station record, its exits..." and every clause carries information, including city-specific last-train behavior and licensing. It is dense and somewhat run-on with nested parentheticals, but not padded or repetitive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool without an output schema, the description explains the main return components, the optional walk behavior, data provenance, and city-specific last-train availability. It leaves some details unspecified, such as the exact structure of the station record and exit fields, but is largely sufficient to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: station accepts common spellings such as Myeong-dong, Hongik Univ. and 명동역, and "to" specifically triggers the walk to a destination record. That clarifies output behavior tied to a parameter rather than merely restating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: the station record, its exits, last-train times by line and direction, and an optional walk to a destination when "to" is supplied. It is easy to distinguish from siblings such as find_active_popups or plan_local_route, though it does not explicitly name or contrast those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the "to" parameter, which adds a walk to a destination record, and through accepted station identifiers. There is no explicit when-to-use versus when-not-to-use guidance, nor a direct pointer to search_verified_places or plan_local_route for related tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources