Skip to main content
Glama

Transita MCP

Visa details

transita_visa_details
Read-onlyIdempotent

Fetch full details for a single visa pathway: eligibility category, processing time, fees, validity, PR timeline, and a free preview of the document checklist (lead time, ancillary cost, first section). The full multi-section checklist is part of Transita's paid action plan, which lives 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_visa_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
visa_idYesTransita visa id, e.g. 'es-digital-nomad'. Get ids from transita_match_visas or transita_list_visas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / visa_id / description
      Added value: +"Transita visa id, e.g. 'es-digital-nomad'. Get ids from transita_match_visas or transita_list_visas."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds a genuinely useful behavioral fact beyond those: the checklist returned is only a free preview (lead time, ancillary cost, first section) and the full multi-section checklist is a paid product on the website — an important expectation-setting boundary.

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?

Two sentences, zero redundancy. The payload list is front-loaded and the paid-content caveat follows immediately, so the agent learns both what it gets and what it does not before committing to a call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the return-value burden and does so by enumerating the fields returned and qualifying the checklist preview. For a single-record read tool backed by full annotations and a fully documented parameter, nothing an agent needs to call it correctly is missing.

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 a single required parameter with 100% schema description coverage, and that schema already explains the id format and points to transita_match_visas and transita_list_visas for discovery. The description adds no syntax, format, or validation detail for visa_id, so the schema does the work and the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and scope: 'Fetch full details for a single visa pathway,' then enumerates the exact fields returned (eligibility category, processing time, fees, validity, PR timeline, checklist preview). The word 'single' plus 'visa pathway' clearly separates it from list/match/compare siblings.

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?

The description implies the right use case (retrieve details for one known visa id rather than browsing), but it never explicitly says when to use this versus transita_match_visas, transita_list_visas, or transita_get_checklist. The id-sourcing guidance lives in the schema, not the description, so usage is only implied here.

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