Skip to main content
Glama

mcp-server

by io.github.mirabello-consultancy
OverviewDiscussionsAdmin

Check Visa-Free Access

check_visa_free
Read-only

Mobility for a programme passport: visa-free count and access to key destinations (Schengen, UK, USA, China).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destinationNooptional: check access to a specific destination (e.g. Schengen, UK, USA, China)
programme_idYesProgramme id as returned by list_programmes (e.g. "st-kitts-cbi"). Not a country name and not a website slug.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the request could not be fulfilled.
termsNoAcceptable-use and information-not-advice terms.
sourceNoAttribution for the data, when it is not Mirabello Consultancy itself.
book_urlNoLink to request a consultation with a Mirabello specialist, for a personal case.
providerNoAlways "Mirabello Consultancy".
disclaimerNoInformation, not legal/tax/financial/immigration advice; figures indicative.
data_updatedNoDate the underlying dataset was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / book_a_consultation
      Removed value: -{
-  "description": "URL to book a Mirabello consultation.",
-  "type": "string"
-}
    • addedOutput schema / properties / book_url
      Added value: +{
+  "description": "Link to request a consultation with a Mirabello specialist, for a personal case.",
+  "type": "string"
+}
    • changedOutput schema / properties / source / description
      Previous value: -"Attribution for the data."New value: +"Attribution for the data, when it is not Mirabello Consultancy itself."
  2. Changed2 schema fields changed
    • addedInput schema / properties / programme_id / description
      Added value: +"Programme id as returned by list_programmes (e.g. \"st-kitts-cbi\"). Not a country name and not a website slug."
    • addedInput schema / properties / programme_id / examples
      Added value: +[
+  "st-kitts-cbi"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present.",
+  "properties": {
+    "book_a_consultation": {
+      "description": "URL to book a Mirabello consultation.",
+      "type": "string"
+    },
+    "data_updated": {
+      "description": "Date the underlying dataset was last updated.",
+      "type": "string"
+    },
+    "disclaimer": {
+      "description": "Information, not legal/tax/financial/immigration advice; figures indicative.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only when the request could not be fulfilled.",
+      "type": "string"
+    },
+    "provider": {
+      "description": "Always \"Mirabello Consultancy\".",
+      "type": "string"
+    },
+    "source": {
+      "description": "Attribution for the data.",
+      "type": "string"
+    },
+    "terms": {
+      "description": "Acceptable-use and information-not-advice terms.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / destination
      Added value: +{
+  "description": "optional: check access to a specific destination (e.g. Schengen, UK, USA, China)",
+  "type": "string"
+}
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is well covered. The description adds only that the result includes a count and access to a few named destinations, which is thin given an output schema exists that already defines the return shape.

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, front-loaded sentence with no filler. It is efficient, though the phrasing 'Mobility for a programme passport' is slightly compressed and could more directly lead with the action and its result.

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 simple read-only lookup, most needs are covered: annotations give the safety profile, the output schema explains the return values, and the schema fully documents parameters. The missing piece is sibling disambiguation, but the core operational information is present.

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 description coverage is 100%, so both parameters (including the programme_id-is-not-a-country-name warning and the destination examples) are already documented in the schema. The description's mention of Schengen/UK/USA/China merely echoes the destination examples, adding no new meaning. Baseline 3 applies.

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 clearly identifies the resource and the payload: visa-free count plus access to key destinations for a given programme passport. It is understandable on its own, but it never distinguishes this tool from close siblings like check_visa_requirement, list_visa_free_destinations, or get_mobility_optionality.

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?

There is no explicit when-to-use or when-not-to-use guidance. With several overlapping siblings (check_visa_requirement, list_visa_free_destinations, get_mobility_optionality), the absence of routing guidance forces the agent to guess which mobility tool to call.

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

All mcp-server 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