Skip to main content
Glama
Sign In

Transita

by io.github.snenenenenenene
OverviewDiscussionsAdmin

Compare visas

transita_compare_visas
Read-onlyIdempotent

Compare 2 or 3 visa pathways side by side: processing time, cost, validity and PR route for each, then which one is quickest to process, which costs least and which lead to permanent residency.

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_ids": "<visa_ids>"
    },
    "name": "transita_compare_visas"
  }
}

Input Schema

NameRequiredDescriptionDefault
visa_idsYes2 or 3 Transita visa ids, e.g. ['us-o1a', 'de-blue-card'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / visa_ids / description
      Added value: +"2 or 3 Transita visa ids, e.g. ['us-o1a', 'de-blue-card']."
  2. First observed

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, closed-world and non-destructive, so safety is covered. The description adds genuinely new behavioral detail: the fields being compared (processing time, cost, validity, PR route) and the derived verdicts (quickest, cheapest, leads to PR), which tells the agent what the response will contain.

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 sentence, front-loaded with the verb and the compared dimensions, with the derived answers appended in priority order. Every clause carries information; only the long trailing list of 'which one...' clauses adds slight density.

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?

The tool is a single-parameter read with no output schema, so the description must convey the return shape — it does so by enumerating the four compared attributes plus the three computed verdicts. Nothing an agent needs in order to decide and call 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?

Schema coverage is 100% and the single parameter is fully documented, including the 2-3 item constraint and an example. The description's '2 or 3 visa pathways' only echoes the minItems/maxItems already in the schema, adding no new syntax or format guidance.

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 states a specific verb and resource (compare visa pathways) and pins the scope to exactly 2 or 3 entries, which matches the schema bounds. It does not explicitly contrast with the nearest sibling, transita_visa_details (single-visa lookup) or transita_match_visas, so an agent must infer the distinction.

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 'compare ... side by side', which makes the multi-visa case obvious, but the description never says when NOT to use it or which sibling to reach for instead (e.g. visa_details for one visa, match_visas for finding candidates). Adequate but leaves routing to inference.

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