Skip to main content
Glama

GoodbyeMatrix Residency & Citizenship Index

Get CBI cost estimate

get_cbi_quote
Read-onlyIdempotent

Answers how much citizenship by investment or a second passport costs for a person or family, or compares programmes by total cost. Calculates the indicative cost for a family: government contribution, investment, fees, professional fees, payment phases and total in USD, plus which family members are eligible, processing time, page links and quoteRequestUrl. With one programme it returns that programme; without program it compares all 9 programmes (St Kitts and Nevis, Antigua and Barbuda, Dominica, Grenada, Saint Lucia, Vanuatu, Sao Tome and Principe, Nauru, Argentina). Figures are rounded indicative figures (total to the nearest 1,000 USD), binding only after a pre-check; the user receives the exact amounts by requesting the cost breakdown through quoteRequestUrl. Read-only: it only retrieves and computes from the GoodbyeMatrix data set, stores nothing, sends nothing and calls no external services.

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": {
      "family": "<family>"
    },
    "name": "get_cbi_quote"
  }
}

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.
programNoProgramme 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. Without a programme, the figures cover all programmes at once.
languageNoResponse language: "en" (English, default) or "de" (German).en

Output Schema

NameRequiredDescriptionDefault
okYes
pagesNo
routeNo
scopeYes
totalNoTotal in USD, rounded to the nearest 1,000.
noticeNo
schemaYes
statusNook, partial, review_required, fees_on_request or not_eligible (main applicant excluded by nationality or country of birth: no figures, no link).
programNoProgramme key.
variantNo
currencyNo
languageYes
programsNo
roundingNo
totalScopeNototal, or known_costs when professional fees are on request.
costSummaryNocontribution, investment and professionalFees as published; fees = total minus the other three.
eligibilityNo
generatedAtNo
overviewUrlNoPortfolio only: overview page of all programmes with the family filled in.
programLabelNo
paymentPhasesNo
pricingNoticeNo
processingTimeNo
quoteRequestUrlNoLink to the calculator page of the programme on goodbyematrix.com with the family already filled in; there the user requests the detailed cost breakdown with the exact amounts. null when not_eligible.
restrictionNoteNoOnly with status not_eligible: why the programme is not possible.
websiteEstimateNoThe figure the website calculator shows.
restrictionsCheckedNotrue when nationalities or a country of birth were given and checked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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."
    • removedOutput schema / properties / dataStatus
      Removed value: -{
      -  "description": "Note on the data status in German and English: calculated live, status = date of the response.",
      -  "properties": {
      -    "de": {
      -      "type": "string"
      -    },
      -    "en": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / properties / rulesChangedAt
      Removed value: -{
      -  "description": "Last change to prices or rules (UTC date, YYYY-MM-DD).",
      -  "type": "string"
      -}
    • removedOutput schema / properties / updatedAt
      Removed value: -{
      -  "description": "Data status: the date of the response (UTC, YYYY-MM-DD). Prices and rules are maintained continuously and every response is calculated live, so the data status is the date of the response in every case, not an older date.",
      -  "type": "string"
      -}
  2. Changed6 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."
    • addedOutput schema / properties / dataStatus
      Added value: +{
      +  "description": "Note on the data status in German and English: calculated live, status = date of the response.",
      +  "properties": {
      +    "de": {
      +      "type": "string"
      +    },
      +    "en": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / rulesChangedAt
      Added value: +{
      +  "description": "Last change to prices or rules (UTC date, YYYY-MM-DD).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / updatedAt
      Added value: +{
      +  "description": "Data status: the date of the response (UTC, YYYY-MM-DD). Prices and rules are maintained continuously and every response is calculated live, so the data status is the date of the response in every case, not an older date.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that figures are rounded indicative estimates (total to the nearest 1,000 USD), binding only after a pre-check, that the exact amounts come via quoteRequestUrl, and which fields the calculation returns. The read-only/no-storage/no-external-calls statement partly echoes the annotations but is reinforced with concrete behavioral detail.

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-loaded with the core answer and well organized, but the trailing read-only sentence partially duplicates the annotations and the programme enumeration is long. Most sentences still earn their place by adding scope or caveats.

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?

For a 3-parameter read-only tool with a rich output schema, the description covers purpose, both operating modes, output contents, rounding/binding caveats, and data provenance. An agent has everything needed to invoke it correctly; return values needn't be re-explained given the output schema.

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 family, program, and language. The description's note that omitting program compares all 9 programmes largely restates the schema's own default clause, adding little beyond what is already structured. 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?

States a specific verb and resource — calculating indicative citizenship-by-investment cost for a person/family and comparing programmes — plus the exact scope (single programme vs all 9). The dual-mode behavior ('with one programme it returns that programme; without program it compares all 9 programmes') lets an agent distinguish it from list_cbi_programs and request_cost_breakdown_link without opening a schema.

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?

Clearly frames the use case (estimating cost / comparing programmes by total cost) and routes the user to quoteRequestUrl for binding exact amounts, which implicitly signals when the request_cost_breakdown_link sibling applies. However, it never explicitly names or excludes the siblings (list_cbi_programs, request_cost_breakdown_link), so the alternative selection is left partly to inference.

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