Skip to main content
Glama
Sign In

stakechain

by io.github.Abstract36
OverviewDiscussionsAdmin

market_profile

Risk profile for one market, for the moment before capital is committed.

Use this when a specific market has been chosen and the question is whether to go ahead. It is the one tool that answers 'what else should I know besides the rate'.

Use something else when: you are still choosing between markets (list_base_yields, best_yield); you only want to know whether the rate moved (yield_history); you need the deposit address (list_lending_vaults).

Prerequisite: the market must be on this server's shelf — a vault, reserve or pool from list_lending_vaults. Arbitrary pool ids from list_base_yields will not resolve.

Returns score (0-100) and band ('solid', 'fair', 'thin' or 'fragile'), plus a signals object holding the six inputs behind it: size (TVL), track_record (days running), stability (APY volatility from daily snapshots), yield_quality (share of the APY that is borrower interest rather than incentives that can stop), cost (the curator's percentage cut) and diversification (share sitting in the largest position). Each signal carries its raw value and its sub-score, and method.weights gives the weighting, so the score can be recomputed. A signal lacking data reports score null and is excluded from the weighting rather than guessed at. Pair with yield_history for an unusually high rate. Describes what has happened, not what will.

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": "market_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolYesVault symbol, address, or protocol-asset (e.g. sparkusdc, aave-usdc)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It does so thoroughly: it describes the returned score/band/signals, the six underlying inputs, weighting recomputation, null handling for missing signals, and the important limitation that it describes past behavior rather than predicting future outcomes.

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?

The description is long but well structured and front-loaded: purpose first, then when/when-not to use it, then prerequisites, then return details. Every paragraph carries decision-relevant information, especially because there is no output schema to explain the return shape elsewhere.

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?

There is no output schema, but the description fully explains the return object, the meaning of `score` and `band`, the six `signals`, the `method.weights`, and the null-handling rule. Combined with the prerequisite and sibling routing, it gives an agent everything needed to decide whether and how to call it.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds crucial semantic constraints beyond the schema: the pool must be on this server's shelf, such as a vault/reserve/pool from `list_lending_vaults`, and arbitrary pool ids from `list_base_yields` will not resolve. That directly affects how the single `pool` parameter should be supplied.

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?

The description states a specific verb and resource: a risk profile for one market, evaluated before capital is committed. It also explicitly distinguishes itself from the other market/yield tools, so an agent can identify its role without opening the schema.

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?

It gives explicit when-to-use guidance ('when a specific market has been chosen and the question is whether to go ahead') and clear when-to-use-something-else guidance naming `list_base_yields`, `best_yield`, `yield_history`, and `list_lending_vaults`. It also states the prerequisite that the market must come from this server's shelf.

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