Skip to main content
Glama

get_programme

Read-onlyIdempotent

Retrieve a citizenship-by-investment programme by ID to review dated evidence, conditions, coverage gaps and warnings. Use it to check programme details before assessing eligibility or travel waivers.

Instructions

Read-only get programme. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
includeNo
releaseNo

Output Schema

NameRequiredDescriptionDefault
dataYes
coverageYes
evidenceNo
warningsYes
evaluatedAtYes
generatedAtYes
schemaVersionYes
datasetReleaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • addedOutput schema / properties / coverage / properties / statisticsObservations
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / coverage / properties / statisticsSubjects
      Added value: +{
      +  "type": "number"
      +}
  2. First observedv0.1.1

TDQS

B3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the epistemic constraint: preserve evidence dates, conditions, coverage gaps and warnings, and never treat absent context as proof of eligibility. That is genuine behavioral context beyond structured fields, though the instruction is terse and doesn't say what happens if evidence fields are dropped.

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?

Three short sentences with the access mode front-loaded and no filler. It is efficiently sized, though the middle sentence is compressed enough to read as an opaque instruction rather than a disclosure.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not required, and the safety profile is covered by annotations. However, with three parameters at 0% description coverage and no guidance on how this differs from the other programme-family getters, an agent still lacks what it needs to call and interpret this tool reliably.

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?

Schema description coverage is 0% across three parameters (id, include with const "evidence", release), yet the description names none of them. The intent of include="evidence" and the meaning of release versus id are left entirely undocumented, so the description does not compensate for the schema 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" restates the tool name with an access-mode qualifier but never says what a programme record actually contains or how it differs from siblings like get_programme_costs, get_coverage, or get_travel_rule. The verb+resource is identifiable, but the scope is vague enough that an agent cannot confidently route between the programme-family tools from this text alone.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. "Missing context never establishes eligibility or a travel waiver" faintly gestures at get_travel_rule, but it is a caution about interpreting results rather than a routing rule for selecting this tool over a sibling.

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