Skip to main content
Glama
Sign In

Helious market intelligence

by io.helious
OverviewDiscussionsAdmin

Treasury auction results and tails

get_auctions
Read-onlyIdempotent

US Treasury auction results, measured by Helious at the close: the high yield, the tail against the when-issued yield, bid-to-cover against the tenor's twelve-auction average, who bought (indirect, direct, dealer), and the desk's strong, in line or weak verdict. Pass tenor to ask about one part of the curve, like 10-year-note or 30-year-bond, which is what you want for 'how did the last 10-year auction go'. The tail is the number that answers whether an auction was good or bad.

Input Schema

NameRequiredDescriptionDefault
freshNoSet true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key.
limitNoMost auctions to return.
tenorNoOne tenor, like 10-year-note, 30-year-bond or 26-week-bill. Plain forms work too: '10y', '30 year'. Or a whole class: bills, notes, bonds, tips, frn. Or a curve SEGMENT, which is usually what 'the front end / belly / long end of the curve' means: front (bills plus the 2- and 3-year notes), belly (the 5-, 7- and 10-year), long (the 20- and 30-year). Reopenings of a tenor are included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fresh / description
      Previous value: -"Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key."New value: +"Set true to ask for the live view of this one call, for 5 credits, where the connected account otherwise receives it an hour behind. Accepted and free where the account is already live. No effect without a key."
  2. Changed1 schema field changed
    • addedInput schema / properties / fresh
      Added value: +{
+  "description": "Not on Pro or Ultimate? Set this to true and this one call answers live for 5 credits. Left out, Free, Squawk and Starter get the answer an hour behind for 1 credit. Pro and Ultimate are live already, so it costs nothing extra there. No effect without a key.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / tenor / description
      Previous value: -"One tenor, like 10-year-note, 30-year-bond or 26-week-bill. Plain forms work too: '10y', '30 year'. Or a whole class: bills, notes, bonds, tips, frn. Reopenings of a tenor are included."New value: +"One tenor, like 10-year-note, 30-year-bond or 26-week-bill. Plain forms work too: '10y', '30 year'. Or a whole class: bills, notes, bonds, tips, frn. Or a curve SEGMENT, which is usually what 'the front end / belly / long end of the curve' means: front (bills plus the 2- and 3-year notes), belly (the 5-, 7- and 10-year), long (the 20- and 30-year). Reopenings of a tenor are included."
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, so the safety bar is low. The description still adds real domain behavior: results are 'measured at the close', it explains what the tail means for interpretation, and it discloses the buyer categories and verdict fields, none of which appear in annotations. The per-call freshness/credit model is only carried by 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.

Conciseness4/5

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

Front-loads the resource and the metric list, then the tenor guidance, which is a sensible order. The closing line about the tail is interpretive rather than instructional, but it is a single short sentence that earns its place as a hint about which number matters.

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?

No output schema exists, and the description compensates by enumerating what a result contains (yield, tail, bid-to-cover, buyer breakdown, verdict). Combined with the rich parameter schema, an agent has enough to call it correctly; only the live-vs-delayed data behavior is left entirely to the schema.

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%, with the tenor parameter already documenting plain forms, classes, and curve segments in detail. The description restates the tenor idea and gives one example without adding format or syntax beyond the schema, 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?

Names the specific resource (US Treasury auction results) and enumerates the exact metrics returned: high yield, tail vs when-issued, bid-to-cover vs 12-auction average, buyer split, and the desk verdict. It does not explicitly distinguish itself from the closest sibling get_treasury_issuance, but the 'results at the close' framing makes the domain unmistakable.

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?

Offers a useful mapping from a natural user question ('how did the last 10-year auction go') to the tenor parameter, which is genuine usage guidance. However, there is no statement of when to use this tool versus alternatives or prerequisites/exclusions, so it stops short of explicit routing.

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

All Helious market intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources