Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_origami-finance

Paid. Live DeFi yields for origami-finance: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/origami-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_origami-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.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does real work: it discloses the paid model ($0.002 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged, which is valuable retry-safety and billing context. It stops short of describing the response structure (pagination, row shape) or any rate limits, so it is not exhaustive.

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?

Lead with 'Paid.' front-loads the most decision-relevant fact, followed by scope, data fields, pricing, auth and the endpoint URL. The telegraphic sentence fragments are dense and readable, and every clause carries information; only the trailing raw URL feels slightly tacked-on.

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 zero-required-parameter GET with no output schema and no annotations, the description covers purpose, data source, cost, payment rails and auth. It partially compensates for the missing output schema by naming the returned metrics. It does not specify row-level shape or whether cross-chain results are grouped, which is the main remaining gap.

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 description coverage is 100%, so sort, limit and min_tvl_usd are already documented in the schema. The description adds nothing about parameter behavior, such as how min_tvl_usd interacts with the returned row count or how sorting affects truncation. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific resource (live DeFi yields for the origami-finance protocol, pools across chains) and enumerates the returned fields: APY, TVL and 7d APY change, sourced from DefiLlama. Combined with the 'yields_protocol_' naming convention, an agent can distinguish it from chain-, token- and top-level yield siblings 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 Guidelines3/5

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

Usage is implied by the protocol-scoped resource: an agent chooses this when it wants origami-finance pools specifically. However, the description never states explicit selection criteria against alternatives such as buy_yields_top or buy_yields_chain_base, and it gives no exclusions. Payment and auth requirements are covered, but call-routing guidance is left to inference.

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