Skip to main content
Glama
Sign In

Transita

by io.github.snenenenenenene
OverviewDiscussionsAdmin

Country overview

transita_country_overview
Read-onlyIdempotent

Get summary data for a destination country: number of visa pathways, EU member status, score dimensions, drawbacks, top cities with rent ranges, and PR/citizenship timelines.

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": {
      "country_code": "<country_code>"
    },
    "name": "transita_country_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
country_codeYesLowercase destination country code, e.g. 'de', 'ca' or 'uk'. 'gb' also works for the UK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / country_code / description
      Added value: +"Lowercase destination country code, e.g. 'de', 'ca' or 'uk'. 'gb' also works for the UK."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent read, and the description adds valuable return-content detail: visa pathway counts, EU status, score dimensions, drawbacks, cities with rent ranges, and PR/citizenship timelines. It does not describe error behavior or what happens for unsupported countries, but it adds substantial context beyond the annotations.

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?

A single front-loaded sentence with a compact list of return contents; every item adds useful information and there is 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?

With no output schema, the description responsibly enumerates the main returned data categories, and the sole parameter is fully documented in the schema. It still leaves minor gaps around error handling, data freshness, and the exact response shape.

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 only one parameter and schema description coverage is 100%, so the schema fully documents the country_code format and UK alias behavior. The description adds only the phrase "destination country" and no additional parameter constraints, which is adequate but not enriching.

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?

States a specific verb and resource ("Get summary data for a destination country") and enumerates the overview contents, making the tool's scope clear. It does not explicitly distinguish itself from siblings such as transita_visa_details or transita_cost_of_living, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description explains what data is returned but gives no explicit guidance on when to choose this overview versus sibling tools like transita_compare_visas, transita_cost_of_living, or transita_visa_details. Usage is only weakly implied by the word "summary".

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