Skip to main content
Glama

AllVisas

Visa routes of a country

get_country
Read-only

All visa and residence routes of one country (by name, ISO code or slug), each with its category, summary, review status and page URL.

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": "<country>"
    },
    "name": "get_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYese.g. "Germany", "DE" or "germany"

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing the shape of each returned record (category, summary, review status, page URL) in the absence of an output schema, including a review-status field that hints at possible unverified 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?

A single dense sentence with the resource front-loaded and the accepted identifier forms parenthesized inline. No filler, no repetition of the title.

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 one-parameter read tool with full schema coverage and safety annotations, this is nearly complete — it even compensates for the missing output schema by listing returned fields. It does not say whether a country with no routes returns an empty result or an error, nor whether results are ordered, which is the only remaining gap.

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 parameter description already gives examples ('Germany', 'DE', 'germany'), so the schema does the heavy lifting. The description restates the accepted identifier forms and adds 'slug', which is a marginal addition over structured data — baseline 3.

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 resource ('all visa and residence routes of one country') and enumerates the fields returned, so an agent knows exactly what comes back. It implicitly contrasts with the single-route sibling ('All ... routes' vs one route) but never names an alternative, so it stops short of full sibling differentiation.

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 scope ('one country') implies when this is the right call — bulk retrieval of every route for a country — but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_route or check_visa. Guidance is inferred rather than stated.

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.

Resources