Skip to main content
Glama

get_yield_market_detail

Evidence for one Morpho vault: current net APY/TVL, historical APY and TVL series, period statistics, quality flags, allocation, instant-withdrawal liquidity, separated eligibility/readiness status, and timestamp. Rank on evidence.apy.medianPercent: the raw series contains upstream artifacts (points above 3000% APY) so averagePercent is filtered and medianPercent is the robust level. Check evidence.liquidity.redeemableUsd before sizing, since vaults typically run near 90% utilization and only unborrowed supply can be withdrawn on demand. Use before recommending or proposing a deposit.

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": {
      "chainId": "<chainId>",
      "vaultAddress": "<vaultAddress>"
    },
    "name": "get_yield_market_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
apyDaysNoAPY history window, 7–365 days; default 30
chainIdYesFortFi yield-supported chain id
tvlDaysNoTVL history window, 7–365 days; default 90
vaultAddressYesVault address from list_yield_markets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 meaningful work: it discloses upstream data artifacts (APY points above 3000%), explains that averagePercent is filtered while medianPercent is robust, and warns that only unborrowed supply is withdrawable at ~90% utilization. It omits explicit read-only framing, auth requirements, and pagination/response shape, so not a full 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 payload inventory, then two actionable cautions. Dense but nearly every clause carries information; the opening sentence is long and packs eight items, which is justifiable given there is no output schema.

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?

For a read tool with no output schema and no annotations, the description adequately enumerates return fields and the key data-quality caveats an agent needs before acting. Missing only ancillary details such as error behavior for an unsupported chainId/vault pair.

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%, including defaults and ranges for apyDays and tvlDays, so the schema already does the parameter work. The description adds no parameter-level meaning (e.g., how window length affects the returned statistics), which matches the baseline 3.

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?

States a specific verb and resource ("Evidence for one Morpho vault") and immediately enumerates the payload: APY/TVL current and historical, period statistics, quality flags, allocation, instant-withdrawal liquidity, eligibility status, timestamp. This clearly separates it from list_yield_markets and rank_yield_markets as the single-vault deep-dive.

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

Usage Guidelines4/5

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

Gives an explicit trigger ("Use before recommending or proposing a deposit") plus operational pre-conditions for sizing (check redeemableUsd, assume ~90% utilization). It does not name when to prefer list_yield_markets or rank_yield_markets instead, and the instruction "Rank on evidence.apy.medianPercent" could be confused with the sibling rank_yield_markets tool.

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