Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CLO

Paid. Yei Finance (CLO) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CLO.

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_tok_CLO"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 load and does well: it discloses that the call is paid ($0.05 USDC), the accepted payment chains (Base or Solana), that failed calls are not charged, and that no auth is required. It omits rate limits, latency, and response format, which keeps it 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.

Conciseness4/5

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

Front-loads the key signal ('Paid.') before the purpose, then cost, then access constraints, then endpoint. Telegraphic fragments are efficient rather than confusing; the raw URL is the only element of marginal value to an agent.

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?

With no input schema and no output schema, the description must describe the return values, and it does (price, 24h change, market-cap rank). Payment and failure semantics are also covered; only serialization format and freshness/caching behavior are left unstated, which is minor for a single fixed-asset price lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the token is fixed by the tool itself rather than passed as an argument.

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?

Names a specific resource (Yei Finance / CLO) and states exactly what data is returned: live USD price, 24h change, and market-cap rank. That distinguishes it from the hundreds of sibling buy_tok_*/buy_coin_* entries by token, but it never contrasts itself with the generic buy_crypto_price tool, so the agent must infer which one to prefer.

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 data it returns ('use this to get the CLO price'). There is no explicit when-to-use versus buy_crypto_price or the buy_coin_CLO-style variants, and no stated prerequisites beyond 'no account, no API key', which is a helpful but partial condition.

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