Skip to main content
Glama

get_programme_statistics

Read-onlyIdempotent

Retrieve read-only statistics for a citizenship-by-investment programme, including evidence dates, conditions, coverage gaps, and warnings; missing context never confirms eligibility or travel waiver.

Instructions

Read-only get programme statistics. Preserve evidence dates, conditions, coverage gaps and warnings. Missing context never establishes eligibility or a travel waiver.

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": {
      "id": "<id>"
    },
    "name": "get_programme_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
cursorNo
includeNo
measureNo
releaseNo

Output Schema

NameRequiredDescriptionDefault
dataYes
coverageYes
evidenceNo
warningsYes
evaluatedAtYes
generatedAtYes
schemaVersionYes
datasetReleaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description's "read-only" adds nothing. It does add useful behavioral context: results carry evidence dates, conditions, coverage gaps and warnings that must be preserved, and missing data must not be read as a negative eligibility finding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short at three sentences, but the second and third are cryptic fragments whose meaning depends on domain knowledge ("preserve evidence dates, conditions…", "missing context never establishes eligibility"). Useful warnings, but not front-loaded and not clearly connected to what the tool returns.

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

Completeness2/5

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

With six undocumented parameters, pagination via cursor/limit, and a filtering measure enum, the description leaves most of the call contract unexplained. It relies on the output schema for return shape but does nothing to help construct a correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Six parameters with 0% schema description coverage and no explanation in the description of id, measure, release, limit, cursor, or include. The measure enum and include=evidence const are left entirely for the agent to infer, which is a substantial gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read-only get programme statistics" names the resource (a programme's statistics) but essentially restates the tool name; it doesn't say which statistics or how it differs from siblings like get_programme, get_programme_costs, or get_coverage. An agent can infer it fetches aggregate metrics but not which ones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus get_programme_costs or get_coverage. The closing line about missing context and eligibility/travel waivers is a caution about interpretation, not guidance on tool selection.

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