Skip to main content
Glama

compare_programmes

Read-onlyIdempotent

Compare up to four citizenship-by-investment programmes side by side, preserving evidence dates, conditions, coverage gaps and warnings so you can assess differences without inferring eligibility.

Instructions

Read-only compare programmes. 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": {
      "ids": "<ids>"
    },
    "name": "compare_programmes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
includeNo
releaseNo
scenarioNo

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new interpretive context: results carry evidence dates, conditions, coverage gaps and warnings, and missing context must not be read as eligibility or a travel waiver — a substantive caveat about how to consume the output.

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, front-loaded with the operation and its read-only nature. The later sentences drift toward instructions for interpreting output rather than describing the tool, but they are terse and carry real information.

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?

The output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a four-parameter tool with zero schema descriptions, the omission of any parameter semantics (what 'release' and 'scenario' select, the 2-4 id bound) leaves a real gap an agent must guess around.

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 four parameters, and the description names none of them. The required 'ids' array, the 'include="evidence"' constant, and the opaque 'release' and 'scenario' selectors are left entirely to the agent's inference; only the word 'evidence' glancingly echoes the include parameter.

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?

States a specific verb and resource ('compare programmes') and prefixes it with 'Read-only', so the agent knows this is a non-mutating comparison over programme records. It is clearly distinct from list_programmes or get_programme by the verb alone, though it never says what dimension of comparison is produced (costs, coverage, rules).

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 when-to-use guidance: nothing says to prefer this over get_programme when evaluating multiple programmes, nor that 2-4 ids are required. 'Read-only' is the only usage-relevant cue, and that is already conveyed by the annotations.

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