mcp-server

Compare Treaty Position

compare_treaty_position

Read-only

Double-tax-treaty position for a relocation corridor (from→to): is a DTA in force, the residence tie-breaker test, treaty withholding rates (dividends/interest/royalties), and any limitation-on-benefits/principal-purpose test. Use ISO alpha-2 codes. Indicative, not advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes	End of the date range, ISO date (YYYY-MM-DD).
`from`	Yes	Start of the date range, ISO date (YYYY-MM-DD).

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.

Changed4 schema fields changedSep 23, 2026
- addedInput schema / properties / from / description
```
Added value: +"Start of the date range, ISO date (YYYY-MM-DD)."
```
- addedInput schema / properties / from / examples
```
Added value: +[
+  "2026-01-01"
+]
```
- addedInput schema / properties / to / description
```
Added value: +"End of the date range, ISO date (YYYY-MM-DD)."
```
- addedInput schema / properties / to / examples
```
Added value: +[
+  "2026-12-31"
+]
```

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 27, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive, so the bar is lower. The description adds useful behavioral context by specifying what aspects are evaluated and adding the caveat 'Indicative, not advice,' which clarifies reliability expectations. No contradiction with annotations is present.

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?

The description is concise, front-loads the core purpose, and avoids redundancy with the schema and annotations. It earns a high score for efficiency, though the conflicting parameter instructions prevent full marks.

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?

The description covers output themes and the non-advice caveat, and the presence of an output schema reduces the need to explain return values. However, the parameter confusion is a substantial completeness gap: an agent cannot reliably call this tool without resolving whether inputs are country codes or dates.

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

Parameters1/5

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

Schema coverage is 100%, but the description introduces a serious mismatch: it says 'Use ISO alpha-2 codes' while the schema clearly defines 'from' and 'to' as ISO dates representing a date range. This conflicts with the schema's examples and descriptions, actively misleading an agent about what the parameters mean.

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 tool's function: assessing double-tax-treaty position for a relocation from one jurisdiction to another, including DTA status, tie-breaker rules, withholding rates, and limitation-of-benefits tests. It is specific enough to distinguish from other tax-related siblings, though it does not explicitly name an alternative.

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?

The description implies the intended use case through 'relocation corridor' and provides the operational instruction 'Use ISO alpha-2 codes.' It does not, however, state when to prefer this tool over siblings like withholding_map or get_country_tax, and no exclusion criteria are given.

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.