mcp-server

Estimate Total Cost

estimate_total_cost

Read-only

Estimate the total cost of a programme for a given family: investment + government & due-diligence fees + family add-ons. Indicative; excludes professional/property/legal fees.

Input Schema

TableJSON Schema

Name	Required	Description
`adults`	No	main + spouse/adult applicants (default 1)
`programme_id`	Yes	Programme id as returned by list_programmes (e.g. "st-kitts-cbi"). Not a country name and not a website slug.
`children_16plus`	No	Number of dependent children aged 16 or over — usually priced higher than under-16s.
`children_under16`	No	Number of dependent children aged under 16 — priced separately by most Caribbean programmes.

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.

Changed6 schema fields changedSep 23, 2026

addedInput schema / properties / children_16plus / description

Added value: +"Number of dependent children aged 16 or over — usually priced higher than under-16s."

addedInput schema / properties / children_16plus / examples
```
Added value: +[
+  1
+]
```

addedInput schema / properties / children_under16 / description

Added value: +"Number of dependent children aged under 16 — priced separately by most Caribbean programmes."

addedInput schema / properties / children_under16 / examples
```
Added value: +[
+  1
+]
```

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"
+]
```

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

First observedJun 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds valuable behavioral context: the estimate is 'indicative' and excludes certain fee categories, which sets expectations about accuracy and scope. It doesn't describe the output format, but the output schema exists and covers that.

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?

Two sentences with zero waste. The core action and scope are front-loaded, and the exclusions are stated in a compact second sentence. Every word earns its place.

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 read-only estimation tool with a full output schema and 100% parameter coverage, the description is nearly complete. The only minor gap is that it doesn't explicitly state that programme_id must come from list_programmes, but the schema already covers that. The description's exclusions and 'indicative' qualifier add the necessary context beyond structured fields.

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 the schema already documents all four parameters. The description adds the high-level context that the estimate is for a 'family' and includes 'family add-ons', which maps to the children/adults parameters, but it doesn't add detail beyond what the schema provides. 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 states a specific verb ('Estimate'), a specific resource ('total cost of a programme for a given family'), and the exact components included ('investment + government & due-diligence fees + family add-ons'). It also explicitly excludes professional/property/legal fees, which distinguishes it from other cost-related tools and clarifies its scope.

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?

The description clearly implies when to use this tool: when an indicative total cost estimate for a family is needed. It does not explicitly name alternatives or exclusions, but the explicit exclusion of professional/property/legal fees and the 'indicative' qualifier provide clear context. It could be improved by naming a sibling like compare_programmes or estimate_timeline as an alternative for different needs.

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.