Skip to main content
Glama

Tape — Hyperliquid Analytics

US Treasury Curve

tape_treasury_curve
Read-onlyIdempotent

US Treasury par yield curve (official Daily Treasury data) with implied forward rates (1y1y, 2y3y, 5y5y), NY Fed reference rates (EFFR/SOFR), upcoming Treasury auctions, and an AI plain-English curve read. Result carries provenance (Treasury and NY Fed sources with their own as-of dates). In hosts that support MCP Apps this renders as a yield-curve chart. For educational purposes only. Not trading advice. Not investment advice. Independent. Not affiliated with Hyperliquid Labs or the Hyperliquid Foundation.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tape_treasury_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
  2. 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 readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description goes further by disclosing that results carry a `provenance` object with per-source as-of dates and that MCP Apps-capable hosts render a chart instead of raw data. It does not discuss freshness or rate limits beyond the as-of point, but for a static official-data lookup the added context is solid.

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

Conciseness3/5

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

The data content is front-loaded and dense with useful detail, which is good, but roughly a third of the text is legal boilerplate ('Not trading advice. Not investment advice. Independent. Not affiliated with Hyperliquid Labs or the Hyperliquid Foundation.'). That repetition consumes budget without helping the agent select or call the tool.

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 parameters and no output schema, the description carries the return-value burden and does it reasonably: it lists the six component families returned plus the provenance wrapper and the chart-rendering caveat. A brief note on payload shape or data latency would close the remaining gap, but nothing essential for a correct call is missing.

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?

The tool takes zero parameters, so the baseline of 4 applies and there is no parameter semantics for the description to compensate for. It correctly says nothing about inputs, avoiding invented arguments.

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

Purpose5/5

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

Names a specific resource (US Treasury par yield curve) and enumerates its actual payloads: par yields, implied forwards (1y1y, 2y3y, 5y5y), NY Fed reference rates, upcoming auctions, and an AI curve read. That content profile is nothing like the crypto/derivatives siblings (tape_liquidation_heatmap, tape_whale_prints), so an agent can route on purpose without inspecting a schema.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of any alternative tool or data source. The only framing sentences are legal disclaimers ('For educational purposes only', 'Not trading advice'), which constrain how the output may be presented rather than telling the agent which tool to pick.

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.

Resources