Skip to main content
Glama

Search visas by nationality

transita_search_by_nationality
Read-onlyIdempotent

List destinations and a suggested visa pathway for citizens of a given country: 4 to 6 destinations, each with key stats, plus an FAQ. Use it when the person asks where they could move and only knows their citizenship. Returns the list of guides if the nationality has no guide yet.

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": {
      "nationality": "<nationality>"
    },
    "name": "transita_search_by_nationality"
  }
}

Input Schema

NameRequiredDescriptionDefault
nationalityYesNationality word or country, e.g. 'Indian' or 'India'. Case does not matter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / nationality / description
      Added value: +"Nationality word or country, e.g. 'Indian' or 'India'. Case does not matter."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral detail beyond that: it returns 4-6 destinations with key stats and an FAQ, and explicitly notes the fallback behavior when no guide exists for the nationality. It does not discuss permissions or rate limits, but those are not critical for this read-only search.

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 tightly written sentences with no filler. The primary purpose and scope come first, followed by the usage condition and fallback behavior, so the most important information is front-loaded.

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?

There is no output schema, so the description carries responsibility for explaining returns. It does this well by specifying 4-6 destinations, key stats, an FAQ, and the no-guide fallback. Exact field names are not given, but the description is sufficient for an agent to understand what to expect from this simple one-parameter search tool.

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 already documents that it accepts a nationality word or country, case-insensitively, with examples. The description reinforces that the input represents citizenship but adds no syntax or formatting details beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource ('List destinations and a suggested visa pathway') plus its scope ('for citizens of a given country'). It also describes the result shape (4-6 destinations with key stats and an FAQ), which clearly distinguishes it from siblings like list_visas, match_visas, and compare_visas.

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?

It gives a clear triggering condition: 'Use it when the person asks where they could move and only knows their citizenship.' It does not explicitly name alternatives such as match_visas or compare_visas, but the usage context is specific enough for an agent to select this tool correctly.

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.