Skip to main content
Glama

defi pool apy

defi-pool-apy
Read-onlyIdempotent

Real APY/TVL from DefiLlama for any protocol/pool. Quick screening Price: $0.02 per call, USDC on Base via x402.

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": {
      "query": "<query>"
    },
    "name": "defi-pool-apy"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesstring (protocol or pool name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely new information — cost ($0.02 per call) and payment mechanism (USDC on Base via x402) — which matters before invoking. It does not disclose what happens on an unknown pool or the shape of the result.

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?

Two short sentences, front-loaded with the value proposition and followed by pricing. Slightly awkward phrasing ('Quick screening Price:') but no wasted content.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with full annotation coverage, the description covers purpose and cost. However, there is no output schema, so the description carries the burden of describing return values (which APY/TVL fields, units, failure behavior for unknown pools) and does so only in passing.

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?

Only one parameter and schema coverage is 100%, so the schema already documents 'query' as a protocol or pool name. The description's 'for any protocol/pool' reinforces that meaning but adds no format, case, or ambiguity-resolution detail beyond the schema.

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 the resource (APY/TVL), the data source (DefiLlama), and the scope ('any protocol/pool'), so an agent knows what it retrieves. It does not distinguish itself from siblings such as token-check or airdrop-score, so it falls short of a 5.

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?

'Quick screening' hints at a use case but gives no explicit when-to-use, when-not-to-use, or alternative tool. With several sibling tools operating on tokens/protocols, an agent gets no routing guidance.

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