Skip to main content
Glama
Sign In

Transita

by io.github.snenenenenenene
OverviewDiscussionsAdmin

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

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower. The description adds genuinely new context: only a free preview of the checklist is returned (lead time, ancillary cost, first section) and the full multi-section checklist is a paid offering off-tool. That paywall boundary prevents an agent from promising complete data.

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, no filler. The returned-field list is front-loaded and the paywall caveat is placed immediately after it, where it is most relevant.

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?

No output schema exists, so the description carries the return-value burden — and it enumerates the returned sections, which is exactly what an agent needs to decide whether to call it. The paid-vs-free split closes the last gap about data completeness.

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 the single parameter's description already gives the id format example and the two sibling tools that supply ids. The prose adds nothing beyond 'a single visa pathway', 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?

Specific verb ('fetch') plus a precise resource ('full details for a single visa pathway'), followed by an enumeration of the returned fields (eligibility, processing time, fees, validity, PR timeline, checklist preview). The word 'single' implicitly separates it from the list/match siblings, though no sibling is named explicitly.

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 makes the use case inferable — pull detail for one visa once you have an id — and hints that id lookup routes through transita_match_visas/transita_list_visas (that hint lives in the schema, not the prose). It never states when not to use it or explicitly contrasts it with transita_compare_visas, which an agent might reach for instead.

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