Skip to main content
Glama

FinanceQuery

Treasury Auction Results

get_treasury_auctions
Read-onlyIdempotent

Get US Treasury securities auction results (bid-to-cover ratio, high yield or discount rate, and the primary-dealer/direct/indirect bidder split), newest first. Set upcoming=true for the announced schedule of auctions not yet held. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
toNoLatest auction date to include, `YYYY-MM-DD`; ignored when `upcoming` is true
fromNoEarliest auction date to include, `YYYY-MM-DD`; ignored when `upcoming` is true
countNoTotal auctions fetched from Treasury, newest first (default: 100); `limit`/`cursor` page through them
limitNoMaximum rows per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
upcomingNoReturn the not-yet-held auction schedule instead of auction records
security_termNoSecurity term filter as Treasury spells it (e.g. "13-Week"); ignored when `upcoming` is true
security_typeNoSecurity class filter ("Bill", "Note", "Bond"); ignored when `upcoming` is true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower; the description still adds real context by disclosing result ordering ('newest first') and that no API key is required. It does not discuss coverage limits of the Treasury dataset or how paging interacts with the count cap, leaving some behavioral detail to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the capability and then the mode switch, with the low-cost 'No API key required' note at the end. No filler, no repetition of schema content.

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

Completeness4/5

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

For a 9-parameter, zero-required tool with no output schema, the description compensates by naming the returned metrics and the sort order, which is most of what an agent needs to decide and call correctly. A brief note on what the filters mean in practice or typical paging volume would close the remaining gap.

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%, and the schema itself already documents date range, count, limit, cursor, fields, upcoming, and the two filters with their 'ignored when upcoming is true' caveats. The description adds nothing about parameter format or interaction beyond echoing the upcoming=true mode, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Get US Treasury securities auction results') and enumerates the returned data (bid-to-cover, high yield/discount rate, bidder split), which pins down scope precisely. It does not explicitly contrast with the sibling get_treasury_yields, so an agent must infer the auction-vs-yield distinction from the names alone.

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?

The one explicit usage rule is 'Set upcoming=true for the announced schedule of auctions not yet held,' which clearly separates the two modes. There is no guidance on when to reach for this tool versus get_treasury_yields or other rates/calendar siblings, nor on default retrieval conditions (the default count/limit behavior lives only in the schema).

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.