Skip to main content
Glama

Zaplanuj wizytę w Stacji Neapol

plan_visit
Read-onlyIdempotent

Użyj, gdy ktoś planuje przyjazd do Stacji Neapol w konkretny dzień: czy będzie otwarte, jak dojechać (pociąg z Wrocławia, ze Świdnicy, po Ślęży albo autem), jak wrócić i czy dla tylu osób trzeba rezerwować. Use when someone plans a visit to Stacja Neapol (pizza near Wrocław) on a given day: opening hours, getting there, getting back, table rules for the party size.

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": {
      "guests": "<guests>"
    },
    "name": "plan_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoData w formacie YYYY-MM-DD (strefa Europe/Warsaw). Brak = dzisiaj. / Date as YYYY-MM-DD; defaults to today.
fromNoSkąd: wroclaw (pociąg z Wrocławia), swidnica, sleza (po zejściu ze Ślęży), car (samochód). / Where from.
guestsYesLiczba osób. / Party size.

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds scope beyond that by listing which facts the answer will cover (hours, outbound travel, return travel, table rules), and phrasing 'czy trzeba rezerwować' implies it reports on reservation policy rather than making a booking. It does not state whether hours are live/current or explicitly disclaim that no reservation is made, which is the kind of extra context that would raise this score.

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?

Two sentences, front-loaded with the triggering situation and then the specific aspects answered; no filler or hedging. The Polish and English sentences are near-duplicates, which is a deliberate localization choice but does double the length without adding new information.

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 aggregation tool with three fully documented parameters and no output schema, the description supplies what is needed to decide and call it: the trigger situation, the aspects covered, and the implicit party-size relevance. Nothing critical is missing, though a note on how results are combined or how current the opening-hours data is would close the remaining gap.

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?

Schema description coverage is 100% and each parameter already documents itself, including the YYYY-MM-DD pattern, the default of today, and the four enum values for 'from'. The description only loosely reinforces this by naming the route options (pociąg z Wrocławia, ze Świdnicy, po Ślęży, autem) and tying 'guests' to table rules, adding little beyond 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 names the concrete resource (Stacja Neapol, pizza near Wrocław) and enumerates the exact questions answered: opening on a given day, transport both ways by train/car, and reservation rules for a party size. That is enough for an agent to see this is a composite 'plan a trip' tool rather than a single lookup. It does not explicitly contrast itself with siblings like is_open_on or get_there_by_train, so differentiation is inferred rather than stated.

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 plans a visit ... on a given day' is an explicit, actionable trigger tied to a user situation. There are no exclusions and no routing advice toward the narrower siblings (e.g., a bare 'are you open today?' could go to is_open_on), which keeps it short of a 5.

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