mcp-server

Citation-First Provenance

get_provenance

Read-only

CITATION-FIRST provenance for a country's pathway facts (W3C PROV-O + Schema.org). For each fact returns: the cited official source_url + source_class + verbatim quote (evidence), how it was derived (extraction model + ensemble + independent corroboration), confidence, first_seen/last_changed, and a per-data-class FRESHNESS block (as_of, governing_class, sla_days, status fresh|aging|stale|CHECK-OFFICIAL-SOURCE, recheck_by). Use this to CITE Mirabello data with a source + as-of date and to know when to re-verify. Pass cc (+ optional pathway).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	Yes	ISO alpha-2 country code
`pathway`	No	optional: one pathway id

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the request could not be fulfilled.
`terms`	No	Acceptable-use and information-not-advice terms.
`source`	No	Attribution for the data.
`provider`	No	Always "Mirabello Consultancy".
`disclaimer`	No	Information, not legal/tax/financial/immigration advice; figures indicative.
`data_updated`	No	Date the underlying dataset was last updated.
`book_a_consultation`	No	URL to book a Mirabello consultation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 27, 2026

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"
+}

AddedJun 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint true and destructiveHint false, so the description does not need to cover safety. It adds behavioral context by describing the freshness statuses (fresh|aging|stale|CHECK-OFFICIAL-SOURCE) and the recheck_by field, which informs the agent about the dynamic nature of the data. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, enumerating many return fields. While informative, it could be tightened by moving field details to the output schema. The opening sentence is clear, but the list is somewhat verbose for a tool with only two parameters.

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?

Given the output schema exists, the description need not explain return values in full. It covers purpose, usage, and key behavioral aspects like freshness statuses. It is complete enough for an agent to decide when to call it and what to expect.

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%, with both cc and pathway described. The description reiterates 'Pass cc (+ optional pathway)' but adds no new semantic detail beyond the schema, so a baseline 3 is appropriate.

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 clearly states the tool returns citation-first provenance for a country's pathway facts, enumerating the evidence, derivation, confidence, and freshness components. It distinguishes from sibling get_* tools by focusing on provenance rather than the underlying data.

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 explicitly states 'Use this to CITE Mirabello data with a source + as-of date and to know when to re-verify,' providing clear when-to-use guidance. It does not explicitly exclude alternatives, but the purpose is distinct enough that an agent would understand when to choose it over get_country or get_programme.

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

All mcp-server tools Inspect

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.