GoodbyeMatrix Residency & Citizenship Index

Get cost breakdown request link

request_cost_breakdown_link

Read-onlyIdempotent

Returns only the personal link (quoteRequestUrl) for one programme and family: the calculator page on goodbyematrix.com with the family already filled in, where the user requests the detailed cost breakdown with the exact amounts by e-mail from the GoodbyeMatrix team. The link carries the family only, never contact details; the user enters their contact details on that page, checks them and sends the request personally; the privacy consent is never preselected. Read-only: it returns a URL only; nothing is sent, booked or stored.

Input Schema

Name	Required	Description	Default
`family`	Yes	Everyone who applies together. The first person is the main applicant (role "main"); only the first person has the role "main". Defaults: a partner counts as married and not same-sex unless stated; a child under 18 counts as dependent. Nationalities and country of birth are relevant for every person in the list (partner, children, parents), not only for the main applicant, because exclusions apply per person.
`program`	Yes	Programme key: sao_tome (Sao Tome and Principe), vanuatu, dominica, st_lucia (Saint Lucia), st_kitts (St. Kitts and Nevis), grenada, antigua (Antigua and Barbuda), nauru, argentina.
`language`	No	Response language: "en" (English, default) or "de" (German).	en

Output Schema

Name	Required	Description
`program`	Yes
`language`	Yes
`programLabel`	No
`quoteRequestUrl`	Yes	Link to the calculator page with the family filled in, where the user enters their contact details and requests the detailed cost breakdown by e-mail.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / family / description

Previous value: -"Everyone who applies together. The first person is the main applicant (role \"main\"); only the first person has the role \"main\". Defaults: a partner counts as married and not same-sex unless stated; a child under 18 counts as dependent."New value: +"Everyone who applies together. The first person is the main applicant (role \"main\"); only the first person has the role \"main\". Defaults: a partner counts as married and not same-sex unless stated; a child under 18 counts as dependent. Nationalities and country of birth are relevant for every person in the list (partner, children, parents), not only for the main applicant, because exclusions apply per person."

changedInput schema / properties / family / items / properties / birthplace / description

Previous value: -"Optional: country of birth as ISO 3166-1 alpha-2 code, as mentioned by the user."New value: +"Optional, per person (not only the main applicant): country of birth as ISO 3166-1 alpha-2 code, as mentioned by the user."

changedInput schema / properties / family / items / properties / nationalities / description

Previous value: -"Optional: every citizenship of this person as ISO 3166-1 alpha-2 codes (for example [\"DE\"] or [\"RU\", \"GE\"] for dual citizens), as mentioned by the user."New value: +"Optional, per person (partner, children and parents included, not only the main applicant): every citizenship of this person as ISO 3166-1 alpha-2 codes (for example [\"DE\"] or [\"RU\", \"GE\"] for dual citizens), as mentioned by the user."

Changed4 schema fields changedOct 21, 2026

removedInput schema / properties / contact

Removed value: -{
-  "additionalProperties": false,
-  "description": "Optional. Contact details are used only as the user has provided them in this conversation and wants to pass them on to GoodbyeMatrix; the link works without them. They prefill the request form on the page; they are not part of the link and the user still checks and sends the request personally.",
-  "properties": {
-    "email": {
-      "maxLength": 254,
-      "type": "string"
-    },
-    "first_name": {
-      "maxLength": 60,
-      "type": "string"
-    },
-    "last_name": {
-      "maxLength": 60,
-      "type": "string"
-    },
-    "phone": {
-      "description": "With international dialling code, for example +49 151 2345678.",
-      "maxLength": 40,
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / contactPrefilled

Removed value: -{
-  "description": "Only when contact was given: true if at least one contact field was accepted and will prefill the form.",
-  "type": "boolean"
-}

removedOutput schema / properties / ignoredFields

Removed value: -{
-  "description": "Only when contact was given: contact fields that were invalid and dropped.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

changedOutput schema / properties / quoteRequestUrl / description

Previous value: -"Link to the calculator page with the family filled in, where the user requests the detailed cost breakdown by e-mail."New value: +"Link to the calculator page with the family filled in, where the user enters their contact details and requests the detailed cost breakdown by e-mail."

First observedOct 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses meaningful behavior: the link carries family data only (never contact details), the user enters and confirms contact details themselves, the privacy consent is never preselected, and nothing is sent or stored. These privacy and consent guarantees are exactly the context annotations cannot convey.

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?

Front-loads the essential fact (returns only the personal link) in the first clause, then adds privacy caveats. It is one long sentence-like block, slightly dense, but every clause earns its place and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, rich annotations, and full schema coverage, the description fills the remaining gaps: what the URL is, what data it does and does not carry, and the consent/non-sending guarantees. An agent has everything needed to decide and invoke correctly.

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%, so program, family and language semantics are fully documented in the schema itself. The description only reinforces that the link 'carries the family' already filled in; it adds no field-level guidance beyond the schema, so baseline 3 applies.

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?

States a precise verb and resource ('Returns only the personal link (quoteRequestUrl)') and scopes it to one programme and family, naming the concrete artifact and the page it points to. The 'only ... link' framing makes clear it is not the quote itself, distinguishing it from get_cbi_quote.

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?

Explains the use case clearly: the user wants to request a detailed cost breakdown by e-mail and the agent supplies the prefilled calculator page. It implicitly contrasts with amount-returning siblings via 'returns only ... nothing is sent, booked or stored', but does not explicitly name an alternative tool for getting actual amounts.

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

All GoodbyeMatrix Residency & Citizenship Index 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.

Resources

Need Help?