Skip to main content
Glama
Sign In

Transita

by io.github.snenenenenenene
OverviewDiscussionsAdmin

Recent rule changes

transita_recent_rule_changes
Read-onlyIdempotent

What changed lately for one destination country: recorded changes to its visa rules or official source pages, plus dated news that cites an official source. Each item carries its source and date. An empty list is the normal answer when nothing has changed.

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": {
      "country": "<country>"
    },
    "name": "transita_recent_rule_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesLowercase destination country code, e.g. 'de', 'ca' or 'uk'. 'gb' also works for the UK.
since_daysNoHow many days back to look, e.g. 60. Default 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: each item carries its source and date, and an empty result is expected rather than an error. It omits the 365-day lookup ceiling, but that lives in the schema.

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

Conciseness5/5

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

Three short sentences, each doing distinct work: what is returned, what each item contains, and how to read an empty result. The return-content detail is front-loaded with no filler.

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 two-parameter read tool with full schema coverage and no output schema, the description covers return shape (items with source and date) and the empty-result case. The only meaningful gap is not routing the agent away from the near-identical transita_rule_changes sibling.

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%, with country code format and the since_days range/default fully documented in the schema. The description only reinforces that a single destination country is scoped per call, adding little beyond the structured fields. Baseline 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 specific resource and scope: recorded visa-rule/source-page changes for one destination country, plus dated news citing an official source. That is far more concrete than the bare name. It does not, however, distinguish itself from the sibling transita_rule_changes, leaving an agent to guess which of the two to call.

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 by 'what changed lately' and the note that an empty list is the normal answer, which usefully discourages an agent from retrying or treating emptiness as failure. But there is no explicit when-to-use versus transita_rule_changes or transita_programme_status, and no stated exclusions.

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

All Transita toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources