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.
providerNoAlways "Mirabello Consultancy".
disclaimerNoInformation, not legal/tax/financial/immigration advice; figures indicative.
data_updatedNoDate the underlying dataset was last updated.
book_a_consultationNoURL to book a Mirabello consultation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
+}
  3. 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"
+}
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds that the tool returns a visa-free count and per-destination access, but discloses nothing about how the count is aggregated, data freshness, or behavior when no destination is given. This is useful context above annotations 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 with no filler; the destination list is concrete and useful. The opening phrase 'Mobility for a programme passport' is slightly abstract, but the description earns its length.

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?

An output schema exists, so return values need no explanation; annotations cover the safety profile; and the two-parameter schema is fully documented. The only meaningful gap is lack of disambiguation from closely related visa siblings (check_visa_requirement, list_visa_free_destinations), which is not fatal for correct invocation given the clear schema.

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%, including strong guidance that programme_id is a list_programmes ID, 'not a country name and not a website slug,' so the schema carries the parameter meaning. The description's destination examples (Schengen, UK, USA, China) duplicate what the schema already says, adding no new parameter semantics.

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 states a specific resource (programme passport) and outputs (visa-free count and access to key destinations, naming Schengen, UK, USA, China). The verb 'check' is only carried by the name/title, and the description does not explicitly distinguish itself from the sibling check_visa_requirement, but the resource and output are concrete enough for an agent to grasp the core function.

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?

There is no explicit when-to-use or when-not-to-use guidance, and closely related siblings like check_visa_requirement and list_visa_free_destinations are never mentioned. The 'Mobility for a programme passport' framing only weakly implies a mobility-assessment scenario, so an agent must infer when this tool is the right choice.

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