Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_tori-finance

Paid. Live DeFi yields for tori-finance: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/tori-finance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
sortNotvl (default) or apy
limitNoRows, 1-100 (default 20)
min_tvl_usdNoMinimum pool TVL in USD (default 100000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well on the operational side: it discloses that the call is paid ($0.005 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged — exactly the facts an agent needs before committing spend. It omits rate limits and any hint at response shape or error semantics, so it stops short of 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.

Conciseness5/5

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

Front-loads the critical 'Paid.' flag, then purpose, then cost/auth/failure terms, then the endpoint. Every sentence carries distinct information an agent would otherwise have to discover by trial, and there is no filler.

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 parameterless-required, paid data endpoint with no output schema, the definition covers cost, payment rails, auth posture, failure billing, and the data fields returned — enough to call it safely. The remaining gap is response structure and pagination behavior, which is a minor omission given the simple 3-parameter surface.

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% — sort, limit, and min_tvl_usd are all documented inline with defaults and ranges — so the schema does the heavy lifting and the baseline applies. The description's mention of APY/TVL/7d change loosely signals what 'sort' operates over but adds no format or unit 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?

The description names the resource precisely: live DeFi yield pools for the tori-finance protocol across chains, with the returned fields spelled out (APY, TVL, 7d APY change) and the upstream data source (DefiLlama). An agent can distinguish it from the ~200 sibling buy_yields_protocol_* tools because the protocol is named in the text. It is not verb-led ('returns'/'lists' is implied rather than stated), which keeps it just 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 Guidelines3/5

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

Usage is only implied by the protocol name — the description never says when to pick this over buy_yields_chain_* (chain-level aggregation) or buy_yields_token_* (token-level) alternatives. There are no exclusions, prerequisites, or routing advice beyond the embedded protocol scope. An agent must infer selection from the tool name alone.

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