GoodbyeMatrix CBI Pricing

Get CBI cost estimate

get_cbi_quote

Read-only

Calculates the indicative cost of citizenship by investment 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. 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.

Input Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`pages`	No
`route`	No
`scope`	Yes
`total`	No	Total in USD, rounded to the nearest 1,000.
`notice`	No
`schema`	Yes
`status`	No	ok, partial, review_required, fees_on_request or not_eligible (main applicant excluded by nationality or country of birth: no figures, no link).
`program`	No	Programme key.
`variant`	No
`currency`	No
`language`	Yes
`programs`	No
`rounding`	No
`totalScope`	No	total, or known_costs when professional fees are on request.
`costSummary`	No	contribution, investment and professionalFees as published; fees = total minus the other three.
`eligibility`	No
`generatedAt`	No
`overviewUrl`	No	Portfolio only: overview page of all programmes with the family filled in.
`programLabel`	No
`paymentPhases`	No
`pricingNotice`	No
`processingTime`	No
`quoteRequestUrl`	No	Link 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.
`restrictionNote`	No	Only with status not_eligible: why the programme is not possible.
`websiteEstimate`	No	The figure the website calculator shows.
`restrictionsChecked`	No	true when nationalities or a country of birth were given and checked.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 18, 2026

changedInput schema / properties / family / description

Previous value: -"Everyone who applies together. The first person must be the main applicant (role \"main\"); only the first person may be \"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."

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

Previous value: -"Optional: country of birth as ISO 3166-1 alpha-2 code. Only if the user mentioned it."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: every citizenship of this person as ISO 3166-1 alpha-2 codes (for example [\"DE\"] or [\"RU\", \"GE\"] for dual citizens). Only if the user mentioned it."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."

changedInput schema / properties / program / description

Previous value: -"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. Omit it to get figures for all programmes at once."New value: +"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. Without a programme, the figures cover all programmes at once."

First observedOct 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the description is not burdened with safety basics. It adds valuable behavioural context beyond the annotations: figures are rounded indicating they are indicative (total to nearest 1,000 USD), they are binding only after a pre-check, and exact amounts are obtained by requesting the cost breakdown through quoteRequestUrl. That is meaningful disclosure for a pricing tool. The only weakness is that the description does not discuss data freshness or whether rates vary by date.

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 three sentences, front-loaded with the primary purpose and output inventory. Every sentence carries information, though the list of return fields is dense and could have been compressed. It is well structured but not maximally lean.

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?

The tool has a complete input schema and an output schema, so the description mainly needs to explain purpose, modes, and behavioural caveats. It covers the single-programme versus all-programme distinction and the indicative/binding caveat, which an agent needs when deciding whether to call it. Missing is any mention of performance or whether the calculation depends on external data, but overall it is nearly complete.

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 every parameter and its meaning. The description reinforces that 'program' selects one programme versus comparing all nine, but adds little syntax or format information beyond the schema. With the schema doing the heavy lifting, a baseline score of 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 opens with a specific verb and resource ('Calculates the indicative cost of citizenship by investment for a family') and then enumerates exactly what is produced (government contribution, investment, fees, professional fees, payment phases, total in USD, eligibility, processing time, links). An agent knows precisely what this tool returns and how it differs from list_cbi_programs.

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 states the two operating modes clearly: 'With one programme it returns that programme; without program it compares all 9 programmes.' That tells an agent how the optional parameter changes behaviour, but it does not explicitly name the sibling tools or say when to use list_cbi_programs or request_cost_breakdown_link instead.

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

All GoodbyeMatrix CBI Pricing 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?