Skip to main content
Glama

Treasury-Bill Rates

rates_treasury_bill
Read-onlyIdempotent

Treasury-bill rate series. (Source: BankRegReports.)

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": "rates_treasury_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenor_codeNoBill tenor, e.g. 4w, 8w, 13w.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description contributes nothing beyond a source credit: it does not say what the series covers (maturities, history depth, units, update frequency) or what shape the response takes. A rate-series tool whose name says "series" but whose description never clarifies whether it returns one latest observation or a time series leaves a real behavioral gap.

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?

Two short fragments with zero filler, and the subject is front-loaded. It is efficient, though the terseness borders on under-specification rather than disciplined brevity.

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 simple one-parameter read tool a short description can suffice, but this one omits everything an agent needs to interpret results: frequency of the series, units, historical range, and whether tenor_code is optional (it is not required, yet no default is mentioned). With no output schema, the description should at least sketch the return, and it does not.

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

Parameters3/5

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

Schema coverage is 100% and the single tenor_code parameter is documented with examples (4w, 8w, 13w), so the schema carries the parameter meaning entirely. The description adds no syntax, defaults, or allowed-value information beyond it. Baseline 3 applies when the schema does the heavy lifting.

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?

"Treasury-bill rate series" is effectively a restatement of the title "Treasury-Bill Rates" with a source attribution appended. It identifies the subject matter but supplies no verb and no distinction from sibling rate tools such as rates_deposit, rates_consumer, or treasury_backdrop, so an agent cannot tell exactly what this returns or how it differs.

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, when-not-to-use, or alternative-routing guidance anywhere in the description. Nothing tells an agent why it would pick this over the several other rates_* tools in the catalog. The only added information is the data vendor, which is not selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources