Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ENS

Paid. ENS/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.10 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ENS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 at all, the description carries the full burden and does well: it discloses cost, payment currency and chain, that no credentials are required, and that failed calls are not charged — exactly the traits an agent needs before spending money. It stops short of explaining how the USDC payment is actually settled or how fresh the quoted price is.

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?

Telegraphic but every fragment earns its place: cost and payment terms lead, data contents follow, endpoint URL last. No filler sentences and no repetition of schema or annotations.

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 output schema and no parameters, the description must describe the return payload itself, and it does by naming each metric and both upstream exchanges. What remains thin is the purchase mechanics — an agent cannot tell from this whether calling the tool triggers an on-chain transfer, a prepaid balance draw, or a 402-style payment challenge.

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; baseline 4 applies. The description instead specifies the returned fields and data sources, which is where the real information value sits.

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?

"ENS/USD live: last price, 24h open/high/low, % change, 24h and 30d volume" states a concrete resource and enumerates exactly what data comes back, so an agent knows this is the ENS price feed rather than a generic tool. Sibling differentiation is only implicit (the coin name is baked into the tool name), and the leading "Paid." is a billing flag rather than a purpose statement.

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?

The description gives call prerequisites (paid, $0.10 USDC on Base, no account or API key, failed calls free) which is useful context, but it never says when to pick this over the generic sibling buy_crypto_price or when a cheaper alternative suffices. Usage is implied by the coin name rather than argued.

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