Skip to main content
Glama

Dojazd do Stacji Neapol pociągiem

get_there_by_train
Read-onlyIdempotent

Użyj, gdy ktoś chce dojechać do Stacji Neapol bez samochodu: pociągiem z Wrocławia, ze Świdnicy albo po zejściu ze Ślęży, i wrócić tego samego dnia. Use when someone wants to reach Stacja Neapol without a car: by train from Wrocław, Świdnica or after hiking Ślęża, and get back the same day.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_there_by_train"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoSkąd. / Where from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the answer covers both the outbound trip and a same-day return, which is useful behavioral context beyond annotations. It does not say whether the result is a timetable, a connection list, or schedule validity, leaving return behavior underspecified.

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

Conciseness3/5

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

The content is front-loaded with the trigger phrase, which is good. However, the entire text is duplicated verbatim in Polish and English, roughly doubling the length with zero added information for a reader who understands either language.

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 simple, read-only, single-enum-parameter lookup with no output schema, the definition supplies the trigger condition, the three supported origins, and the same-day round-trip scope. The only real gap is what the response actually contains (schedules vs. route description), which an agent could not infer. That is a modest gap for a tool of this complexity.

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

Parameters3/5

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

There is one optional enum parameter with 100% schema description coverage, and the description simply restates the same three enum values (Wrocław, Świdnica, Ślęża) without adding format, defaults, or semantics for the omitted case. With schema coverage this high, the baseline of 3 is appropriate.

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 names a concrete goal — reaching Stacja Neapol by train from three specific origins (Wrocław, Świdnica, or after hiking Ślęża) with a same-day return. That is enough to separate it from siblings like is_open_on or whats_made_here, which are about hours and production rather than transport. It stops short of a crisp verb+resource framing (the action is implied by 'dojechać'/'reach'), but the intent is unmistakable.

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

Usage Guidelines4/5

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

'Use when someone wants to reach Stacja Neapol without a car' gives an explicit triggering condition and implicitly scopes out car-based travel. What is missing is an explicit exclusion or an alternative tool for other travel modes or other destinations. No guiding sibling is named, but the context is clear enough for selection.

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