Skip to main content
Glama

get_changes

Read-onlyIdempotent

Retrieve dated, evidence-qualified change records for CBI programmes, preserving conditions, gaps, and warnings so missing context never proves eligibility or a travel waiver.

Instructions

Read-only get changes. 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
limitNo
cursorNo
includeNo
releaseNo
programmeNo

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

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful domain behavior by saying evidence dates, conditions, coverage gaps, and warnings must be preserved, and that missing context cannot establish eligibility or a waiver. It still omits details such as pagination, cursor behavior, or what the returned evidence contains.

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?

The description is short and front-loads the read-only nature, but the opening sentence is largely tautological and the remaining sentences are domain caveats rather than structured operational guidance. It is concise without being especially informative.

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?

An output schema exists, so return-value details need not be explained here. However, with seven undocumented input parameters and no explanation of what "changes" means or when to use this tool, the description is materially incomplete for the tool's complexity.

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?

The schema has seven parameters with 0% description coverage, and the description explains none of them. It does not clarify the meaning of from, to, limit, cursor, include, release, or programme, leaving required inputs such as from and to completely ambiguous.

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

Purpose2/5

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

"Read-only get changes" largely restates the tool name and never specifies what kind of changes are returned or what resource they belong to. The later sentences add domain constraints but do not clarify the core operation, making it hard to distinguish from siblings such as get_coverage or get_programme.

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?

The description provides no explicit guidance on when to call this tool versus alternatives. The warning that missing context does not establish eligibility or a travel waiver is a behavioral caveat, not a usage rule.

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