Skip to main content
Glama

get_source

Read-onlyIdempotent

Retrieve read-only source evidence for CBI research, preserving dates, conditions, coverage gaps, and warnings so missing context does not imply eligibility or a travel waiver.

Instructions

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

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

C2.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine domain behavior beyond that: evidence dates, conditions, coverage gaps and warnings must be preserved, and absence of context must not be treated as an affirmative eligibility or waiver finding.

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?

It is short and front-loads the read-only nature, but the opening "Read-only get source" is near-tautological and partly redundant with readOnlyHint, while the following sentences are dense domain rules with no structural separation.

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 values need not be explained, but the definition still leaves the resource itself undefined, all three parameters undocumented, and the relationship to sibling retrieval tools unstated for a tool with meaningful domain semantics.

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, so the description carries the burden, yet it explains none of them: the required "id" format, the "include" constant ("evidence") and the "release" selector are all unaddressed. Only a faint link to evidence is implied.

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 description gives a verb and resource ("Read-only get source") plus domain cues (evidence, eligibility, travel waiver), but never defines what a "source" actually is or what it contains, so it is hard to distinguish from siblings such as get_coverage or get_changes without opening the schema.

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 guidance on when to call this versus the numerous sibling get_* tools, and no mention of prerequisites. The only constraint stated is an interpretive caveat ("Missing context never establishes eligibility or a travel waiver"), which is not usage routing.

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