Skip to main content
Glama
Sign In

Helious market intelligence

by io.helious
OverviewDiscussionsAdmin

Curve regime flips

get_curve_history
Read-onlyIdempotent

Past curve regime changes: every flip with its time, what it flipped from, and how the session closed.

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.

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. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the record composition of a flip, but says nothing about pagination, default limits, or the one-hour-delayed live-view behavior that the schema flags as costing 5 credits.

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?

A single front-loaded sentence that names the resource and immediately lists the payload fields. No filler, no restatement of the title.

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 does the necessary work of describing what a returned row contains. It is only slightly short of complete: bounds on history depth and result size are 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% and the parameter docs are unusually rich, including the credit cost and latency trade-off for 'fresh'. The description contributes nothing beyond the schema, which is acceptable given the coverage but earns only the baseline.

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+resource ('past curve regime changes: every flip') and enumerates the returned fields (time, prior regime, session close). This clearly distinguishes it from current-state siblings like get_rates_and_curve and get_treasury_curve, though it never names those siblings explicitly.

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 'past' and 'how the session closed' — an agent can infer this is a historical event log — but there is no explicit when-to-use, no exclusion criteria, and no named alternative among the many curve-related siblings.

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