Skip to main content
Glama

Trading Signals Toolkit

Treasury Auction and Yields Desk

treasury_desk
Read-only

US rates snapshot: Treasury par yield curve 1m-30y with 2s10s, 3m10y, 2s5s and 5s30s spreads and 1-day/1-week/1-month changes in bp; upcoming Treasury auctions with ET close time and minutes-to (reopenings labeled); recent auction results with high yield, bid-to-cover and indirect/direct/dealer shares versus the prior six auctions of the same security, plus a strong/average/weak demand label. Read-only, never places orders. Informational only, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
daysNoUpcoming-auction lookahead in days (default 14)
billsNotrue = bills instead of notes, bonds, TIPS and FRNs
resultsNoNumber of recent auction results (default 6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is partly covered; the description reinforces it with 'Read-only, never places orders,' which matters for a finance tool where an agent might assume execution capability. It also discloses behavioral detail beyond annotations — comparison baselines ('versus the prior six auctions of the same security'), a derived demand label, and ET close timing with minutes-to — but says nothing about data freshness, latency, or failure behavior when no auctions are scheduled.

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?

Front-loaded with the primary payload (yield curve and spreads) before moving to auctions and results, and each clause enumerates a distinct returned field rather than padding. It is dense and long for a single block, but almost no wording is redundant; the disclaimer at the end is short and functional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of describing return values, and it does so thoroughly — curve points, four named spreads, three change windows, auction schedule fields, and result metrics with relative comparison. Combined with fully documented parameters and read-only annotations, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, so all three parameters (days, bills, results) are already documented with defaults and bounds. The description adds only indirect hints — 'prior six auctions' gestures at the results default and the reopening labeling clarifies output rather than input — so the baseline of 3 applies rather than a bonus.

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

Purpose5/5

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

The description names a specific resource (US Treasury par yield curve 1m-30y, spreads, upcoming auctions, recent auction results) with a clear read verb. An agent knows exactly what data comes back without opening the schema, and the scope ('US rates snapshot') is unambiguous against the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the domain framing ('US rates snapshot'), and the closing 'Informational only, not investment advice' sets a boundary on use. However, there is no explicit when-to-use or when-not-to-use guidance and no routing to an alternative sibling (e.g., a session brief or event study) for adjacent rate/macro questions.

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