Skip to main content
Glama
Sign In

Scrutica

by io.github.davidgringras
OverviewDiscussionsAdmin

scrutica_get_sovereign_program

Read-only

Fetch detailed data on a national sovereign AI compute program. Returns: announced_usd, announced_govt_only_usd, committed_usd, disbursed_usd, reality_ratio, status, key_partners, NVIDIA/US dependency, source_count, and published_spending (a government's own spending figures, each in its currency against its budget, with the document). 'list_all' returns a summary table of all tracked programs.

announced_usd can include private commitments; announced_govt_only_usd records the government-funded portion. Compare the programme sources for scope, dates and currency conversions. A government-only figure can still span a different budget period or initiative from another programme's figure. reality_ratio divides disbursed_usd by announced_govt_only_usd, using announced_usd when the government-only field is null. The ratio is null when disbursement or the denominator is missing, or the denominator is zero. Each row includes reality_ratio_denominator_usd and reality_ratio_denominator_field so the division is reproducible from the payload. Where disbursed_usd converts a government's published spending figure, reality_ratio_basis is native_currency and the ratio divides that figure by its own budget in the source currency (reality_ratio_numerator_native / reality_ratio_denominator_native, in reality_ratio_currency): the two dollar amounts were converted on different dates and do not reproduce it. disbursed_usd derives only from a government's published expenditure or payments; a transfer to an administering body is listed in published_spending as released and is not counted. Missing fields and differing reporting scopes limit comparisons; reality_ratio_unavailable_reason explains an absent ratio.

Input Schema

NameRequiredDescriptionDefault
countryNoISO 3166-1 alpha-2
list_allNoReturn summary of all sovereign programs instead of a single record
program_idNoScrutica sovereign-program ID in the form 'sovereign-<country_code>' (e.g. 'sovereign-ae'), as returned by scrutica_search and list_all. The bare country_code is also accepted. Regional programs use non-ISO codes ('sovereign-eurohpc', 'sovereign-nato-aukus', 'sovereign-africa-regional') and are reachable ONLY via program_id or list_all — the 2-letter country parameter cannot match them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / program_id / description
      Previous value: -"Scrutica sovereign-program ID in the form 'sovereign-<country_code>' (e.g. 'sovereign-ae'), as returned by scrutica_search and list_all. The bare country_code is also accepted. Regional programs carry non-ISO codes ('sovereign-eurohpc', 'sovereign-nato-aukus', 'sovereign-africa-regional') and are reachable ONLY via program_id or list_all — the 2-letter country parameter cannot match them."New value: +"Scrutica sovereign-program ID in the form 'sovereign-<country_code>' (e.g. 'sovereign-ae'), as returned by scrutica_search and list_all. The bare country_code is also accepted. Regional programs use non-ISO codes ('sovereign-eurohpc', 'sovereign-nato-aukus', 'sovereign-africa-regional') and are reachable ONLY via program_id or list_all — the 2-letter country parameter cannot match them."
  2. Changed1 schema field changed
    • changedInput schema / properties / program_id / description
      Previous value: -"Scrutica program ID"New value: +"Scrutica sovereign-program ID in the form 'sovereign-<country_code>' (e.g. 'sovereign-ae'), as returned by scrutica_search and list_all. The bare country_code is also accepted. Regional programs carry non-ISO codes ('sovereign-eurohpc', 'sovereign-nato-aukus', 'sovereign-africa-regional') and are reachable ONLY via program_id or list_all — the 2-letter country parameter cannot match them."
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description extensively explains returned fields, data provenance, ratio calculation, denominator basis, currency-conversion caveats, and missing-data limitations. This is unusually strong behavioral disclosure for a read-only retrieval tool.

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 purpose and return fields, then organized into explanatory paragraphs about ratio semantics and caveats. It is long but dense with relevant data-interpretation context, with little obvious filler.

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 no output schema, the description carries the burden of explaining return values and does so comprehensively, including field meanings, ratio derivation, and data-quality limitations. It is complete enough for an agent to interpret and use the result 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 description coverage is 100%, so the input schema already documents country, list_all, and program_id thoroughly. The description reinforces the list_all behavior but adds little parameter meaning beyond what the schema provides.

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: fetching detailed data on a national sovereign AI compute program. It also clarifies the internal list_all mode, but it does not explicitly distinguish this tool from siblings such as scrutica_search or scrutica_get_facility.

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?

Usage is implied by 'Fetch detailed data' and by the note that list_all returns a summary table instead. However, the description does not explicitly say when to use this tool versus scrutica_search or other retrieval tools, nor does it name exclusions.

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

All Scrutica toolsInspect
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