Skip to main content
Glama

list_programmes

Read-onlyIdempotent

List citizenship-by-investment programmes with dated evidence, conditions, coverage gaps and warnings. Filter by jurisdiction, release or stage to check published routes and their limits.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_programmes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
stageNo
cursorNo
includeNo
releaseNo
jurisdictionNo

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

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a useful domain caveat about preserving evidence dates, conditions, gaps, and warnings, and about not inferring eligibility from missing context, but it omits pagination, limits, cursor behavior, and filter behavior.

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 short and front-loads the core purpose in the first sentence. The later sentences are somewhat cryptic but remain compact and do not contain obvious filler.

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?

For a seven-parameter listing tool with an output schema, the description is incomplete: it does not explain how to use the filters, pagination via limit and cursor, or how the evidence-related caveat maps to returned data. The annotations cover safety, but key invocation details are absent.

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

Parameters1/5

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

Schema description coverage is 0% across seven parameters, and the description does not mention any parameter semantics. It says nothing about jurisdiction, release, stage, limit, cursor, include, or kind, so it does not compensate for the missing schema descriptions.

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: 'Read-only list programmes.' This clearly distinguishes listing from mutating operations, though it does not explicitly differentiate itself from sibling tools such as get_programme or compare_programmes.

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?

Usage is only implied by 'list programmes.' The description gives no guidance on when to use this tool versus get_programme, compare_programmes, or other siblings, and it does not explain any prerequisites or filtering conditions.

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