Skip to main content
Glama

get_programme_costs

Read-onlyIdempotent

Retrieve programme costs with evidence dates, conditions, coverage gaps, and warnings; missing context does not establish eligibility or a travel waiver.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYes
optionNo
includeNo
releaseNo
scenarioNosingle_adult

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

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description earns credit for what it adds: results carry evidence dates, conditions, coverage gaps and warnings that must be preserved, and absence of context must not be read as proof of eligibility or a travel waiver. That guardrail on interpreting sparse results is genuine behavioral context not present in the annotations. It stops short of stating whether results can be paginated or how gaps are signalled.

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?

Three short sentences with no filler and the read-only constraint front-loaded, which is structurally sound. However, the terseness tips into opacity — phrases like 'preserve evidence dates' and 'missing context' are compressed to the point that their operational meaning is unclear.

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?

The output schema means return values needn't be explained, and annotations cover the safety profile, so those burdens are lifted. But a five-parameter tool with zero schema descriptions and a non-obvious 'scenario' default demands parameter explanation the description entirely omits, leaving the definition materially incomplete for correct invocation.

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 five parameters, so the description carries the full explanatory burden and fails it. Nothing explains what 'id', 'option', 'release', or 'scenario' (which defaults to 'single_adult') mean, and the const 'include: evidence' is only obliquely echoed by the phrase 'evidence dates'. The agent is left guessing at every argument.

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?

The first sentence restates the tool name ('get programme costs') and adds only 'read-only', which the annotations already declare. It never clarifies what a 'programme cost' comprises (fees, tuition, living costs?) or how it differs from sibling get_programme, get_programme_statistics, or compare_programmes. An agent can identify the resource but not its scope.

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 guidance and no routing to alternatives such as get_programme or compare_programmes. The closing sentence ('Missing context never establishes eligibility or a travel waiver') is an interpretive caveat, not a usage condition, so the agent must infer the calling context.

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