Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "program": "<program>",
      "family": "<family>"
    },
    "name": "request_cost_breakdown_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyYesEveryone 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.
programYesProgramme 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.
languageNoResponse language: "en" (English, default) or "de" (German).en

Output Schema

NameRequiredDescriptionDefault
programYes
languageYes
programLabelNo
quoteRequestUrlYesLink 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.

  1. Changed3 schema fields changed
    • 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. 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."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."
    • changedInput schema / properties / family / items / properties / birthplace / description
      Previous value: -"Optional, per person (not only the main applicant): country of birth as ISO 3166-1 alpha-2 code, as mentioned by the user."New value: +"Optional: 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, 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."New 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."
  2. Changed3 schema fields changed
    • 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."
  3. Changed4 schema fields changed
    • 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."
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only annotations, the description explains that the link carries only family data, never contact details; the user enters and checks contact details personally; privacy consent is never preselected; and nothing is sent, booked, or stored. These are meaningful behavioral and privacy guarantees that an agent could not infer from the annotations alone.

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 front-loaded with the core return value and is mostly free of waste. It is somewhat long and semicolon-heavy, but every clause contributes useful privacy or workflow context.

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?

Given the rich input schema, existing output schema, and annotations, the description is complete enough for correct invocation. It covers what the link is, what it contains, what the user must do, and what the tool does not do.

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%, and the schema already documents program, family, and all nested family fields thoroughly. The description adds only high-level context that the link carries the family, not contact details, but does not add parameter-specific meaning beyond the schema.

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 verb and resource: it returns only the personal quoteRequestUrl for one programme and family. It clearly distinguishes this from a quote by emphasizing that the link is a calculator page where the user requests a detailed cost breakdown by e-mail, but it does not explicitly name or contrast with the sibling tools.

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 gives a clear context for use: the user wants a personal link to request a detailed cost breakdown by e-mail. It does not explicitly state when to prefer this over get_cbi_quote or when not to use it, so the alternative routing is implied rather than fully specified.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources