Transita

List visas

transita_list_visas

Read-onlyIdempotent

Browse the visa catalogue without a profile. Filter by country, category or whether the route leads to permanent residency. Each row gives the id, name, country, government fee, processing time and PR route, so you can pick ids for the other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transita_list_visas"
  }
}

Input Schema

Name	Required	Description
`goal`	No	Main reason for moving, to keep only routes built for it, e.g. 'digital_nomad'.
`limit`	No	Most rows to return, e.g. 20. Default 50.
`country`	No	Lowercase destination country code, e.g. 'de', 'ca' or 'uk'. 'gb' also works for the UK.
`category`	No	Visa category, e.g. 'skilled_worker', 'digital_nomad' or 'student'.
`leads_to_pr`	No	True for routes that lead to permanent residency, false for those that do not, e.g. true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / goal

Added value: +{
+  "description": "Main reason for moving, to keep only routes built for it, e.g. 'digital_nomad'.",
+  "enum": [
+    "work_tech",
+    "start_company",
+    "study_work",
+    "relocate_family",
+    "digital_nomad"
+  ],
+  "type": "string"
+}

AddedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the exact return shape (id, name, country, fee, processing time, PR route) in the absence of an output schema, though it says nothing about ordering or what a broad unfiltered query returns.

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 tight sentences, front-loaded with the core action and scope, then filter capabilities, then return fields and downstream use. 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 read-only list tool with full schema coverage and rich annotations, the description covers purpose, filtering and return fields adequately. The minor gap is that it doesn't mention the `goal` filter or default row limit, though the schema documents both.

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%, so the baseline is 3; the description restates country/category/PR filters but adds no syntax or semantics beyond the schema. It also omits the `goal` and `limit` parameters entirely, so it does not fully mirror what is available.

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?

States a specific verb and resource ('Browse the visa catalogue') plus the defining qualifier 'without a profile', which separates it from the profile-driven match_visas sibling. It also enumerates the fields each row returns, so an agent knows what it gets back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Without a profile' gives clear context for when this is the right entry point, and 'so you can pick ids for the other tools' establishes the downstream workflow. It never names an explicit alternative or exclusion (e.g. 'use match_visas if you have a profile'), so it stops short of full routing guidance.

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

All Transita tools Inspect

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.