Skip to main content
Glama

AllVisas

One visa route with its sources

get_route
Read-only

One visa route by its AllVisas page URL or path: requirements, fees, rights and risks, each with the official source URL, the verbatim quote it rests on or the legal provision, and when the source was read or the statement reviewed.

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": {
      "url": "<url>"
    },
    "name": "get_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYese.g. https://allvisas.com/countries/germany/drafts/work/eu-blue-card/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered externally. The description does add value by disclosing the shape of each returned fact — official source URL, verbatim quote or legal provision, and read/review date — which tells the agent the output is citation-backed. It omits any failure behavior for a bad or foreign URL, so it is additive but not rich.

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?

A single sentence, front-loaded with the resource and key, then the returned fields. It is dense but every clause maps to real content the agent gets back; only the trailing "when the source was read or the statement reviewed" is slightly redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description carries the full burden of explaining what comes back, and while it lists the fact categories and provenance, it never describes the response structure (one object? nested requirement entries? lists?) or error handling for malformed paths. Adequate to invoke, thin for interpreting the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter at 100% schema coverage, the baseline is 3. The description earns an extra point because it broadens the accepted input beyond the schema's single full-URL example, stating that a path also works — meaning the schema does not fully convey.

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 gives a specific verb-plus-resource ("One visa route") and a precise lookup key ("AllVisas page URL or path"), and enumerates the payload (requirements, fees, rights, risks). It does not distinguish itself from siblings like check_visa or get_country, so an agent must infer the boundary, but the scope of this tool is unambiguous.

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 only implied: the agent learns it needs a page URL or path, which suggests this is the follow-up call once a route URL is known. There is no explicit when-to-use, no when-not-to-use, and no named alternative (e.g., use check_visa for a quick yes/no) despite four sibling tools that could plausibly compete.

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