Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SIREN

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

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

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 a solid job: it discloses that the call is paid, the exact price, the accepted payment chains (Base or Solana), that no account or API key is needed, and that failures are not billed. It omits rate limits, response freshness, and what happens if payment settles but the upstream fetch fails.

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?

Five compact fragments, front-loaded with 'Paid' and the returned fields before commercial and access details. Every sentence carries distinct information: cost, rail, auth, billing policy, endpoint. 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 zero-parameter paid endpoint with no output schema, the description covers what is returned, what it costs, how to pay, and the failure-billing policy. Only the shape/format of the returned payload and data freshness are left unstated, which is a minor gap given there is no output schema.

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; the baseline applies. The description correctly implies the token is fixed by the tool itself rather than passed in.

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?

States a specific verb and resource: live USD price, 24h change and market-cap rank for Siren (SIREN). An agent can tell exactly what data comes back. It does not, however, differentiate itself from the generic buy_crypto_price or explain the buy_tok_* family convention, so sibling routing relies partly on the tool name.

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 paid nature and cost are stated ('$0.01 USDC', 'Failed calls not charged'), which implicitly frames usage as a deliberate purchase, but there is no explicit when-to-use guidance or named alternative (e.g., 'for other tokens use buy_crypto_price'). The agent must infer the selection rule from the token symbol in the name.

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