Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_liquity-v1

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

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_liquity-v1"
  }
}

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.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does so well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. It does not state data freshness/latency or what the response envelope looks like when no pools match, which keeps it from 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.

Conciseness4/5

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

It leads with 'Paid.' so cost is front-loaded, then states the resource and fields, then commercial terms, then the URL. Every sentence carries information and there is no filler, though the raw URL tacked on the end is slightly clunky.

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 three-optional-parameter read tool with no output schema, the definition covers purpose, data source, pricing, auth model, and failure billing, which is nearly everything needed to call it correctly. The remaining gaps are minor: nothing about pagination behavior or the shape/ordering of returned pool rows.

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%, with sort, limit, and min_tvl_usd each documented in the schema, so the baseline is 3. The description's mention of APY/TVL loosely maps to the sort options but adds no format, range, or default detail beyond what the schema already provides.

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 a specific resource (live DeFi yields for the liquity-v1 protocol) and enumerates the returned fields: APY, TVL, and 7d APY change sourced from DefiLlama. The protocol slug in the tool name separates it from the many sibling yield tools, but the description never contrasts itself with the adjacent buy_yields_protocol_liquity-v2, so a reader must rely on the name alone for that distinction.

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: the description says what data you get, so an agent infers it should call this when it wants Liquity v1 pool yields. There is no explicit statement of when to prefer this over sibling tools such as buy_yields_protocol_liquity-v2, buy_yields_chain_*, or buy_yields_top, and no prerequisites or exclusions are given.

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