Skip to main content
Glama
Sign In

stakechain

by io.github.Abstract36
OverviewDiscussionsAdmin

yield_history

Daily APY and TVL history for one market, with min, median, max and volatility over the window.

Use this for one question only: has this rate held, or did it appear yesterday? Call it before acting on any unusually high rate.

Use something else when: you want the other risk factors — fee, size, utilisation, concentration — which are in market_profile; you are still choosing a market (list_base_yields or best_yield).

Prerequisite: a market id from one of the list tools. Check observations before concluding anything — a market added recently has few snapshots, and a short series is not evidence of stability.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pool": "<pool>"
    },
    "name": "yield_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, default 30
poolYesMarket id: a pool id from list_base_yields, or vault:<address> from list_lending_vaults

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the prerequisite of a valid market id, warns that a recently added market yields few snapshots, and cautions that a short series is not evidence of stability. It does not mention any limits on the `days` window or response size, which keeps it from a 5.

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-loaded with the purpose, then cleanly segmented into usage, exclusions and prerequisite. Every sentence carries information, though the caveat about `observations` reads as a fourth block that could have been folded into the prerequisite line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 describes the returned series and summary statistics, so an agent knows what comes back. For a two-parameter read tool with no annotations, the prerequisites and interpretation caveats make the definition self-sufficient.

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 both `pool` and `days` are already documented, including the default of 30 days. The description reinforces where the market id comes from and frames the window as a look-back, but adds no format or boundary detail beyond the schema; baseline 3 applies.

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 (daily APY and TVL history for one market) and the derived statistics (min, median, max, volatility) it returns. It is immediately distinguishable from siblings like market_profile (other risk factors) and list_base_yields (market selection).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the single question this tool answers, prescribes calling it before acting on an unusually high rate, and lists named alternatives for the cases it does not cover (`market_profile`, `list_base_yields`, `best_yield`). When-to-use, when-not-to-use and alternatives are all present.

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

All stakechain 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