Skip to main content
Glama
Sign In

Helious market intelligence

by io.helious
OverviewDiscussionsAdmin

Official 17:00 Treasury closes

get_yield_closes
Read-onlyIdempotent

Official 17:00 New York Treasury yield closes per session, as Helious recorded them. Before that ledger began, the official daily Treasury yields back to 2000 (record 'official') when since or before asks for them. Availability follows the connected account.

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 rows to return.
sinceNoOldest date to include, like 2026-06-01. How far back you can go depends on your plan.
beforeNoNewest date to include, like 2018-12-31, to page further back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / before
      Added value: +{
+  "description": "Newest date to include, like 2018-12-31, to page further back.",
+  "type": "string"
+}
  2. 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."
  3. 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"
+}
  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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond that: the ledger start boundary, the 'official' historical record fallback, and that availability is gated by the connected account — useful for an agent deciding whether a call will succeed.

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?

Three sentences, purpose front-loaded, no filler. The middle sentence ("when since or before asks for them") is awkwardly worded and slightly obscures the fallback rule, costing a point.

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, so the description should carry return semantics; it conveys that results are session-based closes plus a historical daily series, which is the essential shape. Pagination depth and row format remain unstated, but for a 4-parameter read tool with full schema coverage and strong annotations this is largely complete.

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%, so the baseline is 3 and the schema already documents fresh, limit, since and before including credit cost. The description adds some meaning by tying since/before to the historical 'official' record, but it does not explain paging interaction between limit and before.

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?

The description names a specific verb+resource: official 17:00 New York Treasury yield closes per session, with a clear historical fallback to official daily yields back to 2000. It is distinguishable from curve siblings by the fixed 17:00 session framing, but it never names get_treasury_curve or get_curve_history to make the boundary explicit.

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?

"when since or before asks for them" implies a usage condition for the historical record, and "Availability follows the connected account" hints at a plan gate. However, there is no explicit when-to-use / when-not-to-use statement and no named alternative among the many rate/curve siblings, so the agent must infer 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