Skip to main content
Glama
Sign In

Transita

by io.github.snenenenenenene
OverviewDiscussionsAdmin

Document checklist

transita_get_checklist
Read-onlyIdempotent

The document checklist for one visa route: how far ahead to start, what the paperwork costs beyond the government fee, the first section in full with where to get each document, and the other sections by name and document count. The complete checklist, with tracking, is part of Transita's paid action plan on the website.

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": {
      "visa_id": "<visa_id>"
    },
    "name": "transita_get_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
visa_idYesTransita visa id, e.g. 'de-eu-blue-card'. Get ids from transita_match_visas or transita_list_visas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world profile, so the description's value is in disclosing result shape: only the first section is returned in full, the rest are summarized by name and count, and the tracked version is paywalled. That is meaningful behavioral context an agent would otherwise not know.

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?

One front-loaded sentence covering contents and the paywall caveat, with zero filler. It is dense and slightly list-like but every clause carries 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?

With no output schema, the description must convey return shape, and it does — partial sections, cost breakdown, lead time, plus the paid-plan limitation. What it lacks is any indication of the item structure or how to follow up on the incomplete sections.

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 the single visa_id parameter is already documented with an example and pointers to transita_match_visas and transita_list_visas. The description adds nothing beyond reinforcing 'one visa route', so the 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 names the specific resource (document checklist for a single visa route) and enumerates what it contains: lead time, extra paperwork costs, first section in full, remaining sections by name and count. This is far more specific than a sibling like transita_visa_details, though it never explicitly contrasts itself with that sibling.

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 only implied — an agent must infer that this is the tool for paperwork questions rather than transita_visa_details. The description does state a boundary (full checklist with tracking lives in the paid plan), which is useful, but there is no explicit when-to-use / when-not-to-use routing.

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