Skip to main content
Glama

Check a travel period

trip_check
Read-onlyIdempotent

For a travel period in Donostia-San Sebastián: festivals and events, holidays of top restaurants, which reviewed places are closed on which weekday, cider house (Txotx) season and seasonal products. Field names and texts are German (feste = festivals, betriebsferien = restaurant holidays, ruhetage = closing days, saison = seasonal products).

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "trip_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast day, format YYYY-MM-DD.
fromYesFirst day, format YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: result content is German-keyed, with an inline glossary (feste, betriebsferien, ruhetage, saison) so the agent can interpret output. It does not describe error behavior or empty-result handling, keeping it below a 5.

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 substantive content list, followed by a compact German-to-English glossary. The glossary is long but every term maps to a named field, so it earns its space. Slight density without paragraphing keeps it from a 5.

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?

With no output schema, the description must convey what comes back; it does so by enumerating the data categories and the German field names an agent will encounter. It remains silent on result shape, volume, or what happens on dates outside coverage, but for a two-date read-only lookup the essential information is present.

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 coverage is 100% and both date parameters carry format documentation, so the schema does the heavy lifting. The description only frames the pair as a 'travel period' without adding constraints such as range limits, ordering, or inclusive-date behavior beyond the schema's 'First day'/'Last day' labels. Baseline 3 applies.

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 specifies the resource clearly: temporal/seasonal information for a travel period in Donostia-San Sebastián, enumerating festivals, events, restaurant holidays, weekday closures, Txotx season, and seasonal products. That enumeration distinguishes it from siblings like find_places or next_departures. It stops short of a crisp verb phrase (e.g. 'returns'), relying on 'For a travel period...' to imply the action.

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 rather than stated: an agent can infer it applies when planning travel to this specific city over a date range. There is no explicit when-not guidance, no prerequisites, and no named alternative among ask_gozatu, search, or find_places for overlapping needs.

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