Skip to main content
Glama
Sign In

Helious market intelligence

by io.helious
OverviewDiscussionsAdmin

Rate path

get_rate_path
Read-onlyIdempotent

What the market is paying for US interest rates up to four years out. Two strips, kept apart because they are DIFFERENT RATES: sr3 is sixteen quarterly 3-month SOFR futures grouped into the whites, reds, greens and blues a rates desk quotes, and ff is forty-eight monthly 30-day fed funds contracts. Every contract carries its implied rate now and the rate the SAME contract carried six and twelve months ago, so the gap is the market changing its mind rather than a different instrument. Rates are percent. These are traded prices and not forecasts. Do not compare the two lanes contract by contract: SOFR is secured and the fed funds effective rate is not, and an SR3 month spans the quarter between two IMM dates while a fed funds month is a calendar month.

Input Schema

NameRequiredDescriptionDefault
laneNosr3 for the quarterly SOFR strip, ff for the monthly fed funds strip. Omit for both.
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.
historyNoAdd each contract's own daily settlement run.

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. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare safety (readOnly, idempotent, non-destructive), so the description adds valuable domain context: rates are traded prices not forecasts, the time-gap comparison reflects market changes not different instruments, and the two lanes are not directly comparable. It omits cost/auth details, which the schema covers.

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?

The description is dense but front-loaded with the core purpose, then moves into necessary caveats. Every sentence carries useful information, though some phrasing (e.g., the lane comparison warning) is lengthy; it remains appropriate for the tool's complexity.

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?

With no output schema, the description explains the return contents (implied rates now plus six and twelve months ago) and warns about non-comparability. It leaves the exact response shape and the effect of the `history` parameter implicit, but covers the essential domain semantics an agent needs.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds substantial meaning to the `lane` parameter by explaining `sr3` (sixteen quarterly 3-month SOFR futures grouped into whites/reds/greens/blues) and `ff` (forty-eight monthly 30-day fed funds contracts). It does not elaborate on `fresh` or `history`, but the schema documents those sufficiently.

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 states a specific resource and scope: 'What the market is paying for US interest rates up to four years out,' with two named strips (`sr3`, `ff`). It is clear what the tool returns, though it does not explicitly differentiate itself from siblings like `get_rates_and_curve` or `get_treasury_curve`.

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?

The description gives important interpretation guidance ('Do not compare the two lanes contract by contract') but does not say when to use this tool versus alternatives such as `get_rates_and_curve` or `get_curve_history`. The agent must infer selection from the resource description alone.

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