Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BROCCOLI

Paid. CZ's Dog (BROCCOLI) 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/BROCCOLI.

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

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 supplied, the description carries the full burden and does well: it flags the tool as paid, names the exact price ($0.01 USDC), the two accepted chains, the no-auth posture, and the failure-billing policy. Missing only rate limits, latency, and what a successful response payload looks like (no output schema exists to cover that gap).

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-loaded with the paid flag and the deliverable, then commercial terms, then the endpoint URL. Every fragment carries information, though the telegraphic style ('Paid.', 'URL ...') reads like a listing rather than prose and the URL is arguably redundant with the tool name.

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, single-value quote tool, the description covers the essentials an agent needs: what data comes back, what it costs, how to pay, and that failures are free. It lacks only response-shape detail, which no output schema supplies, and sibling routing.

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 and the input schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the token is fixed by the endpoint 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 resource (CZ's Dog / BROCCOLI price) and enumerates exactly what is returned: live USD price, 24h change, market-cap rank. An agent can tell this is a single-asset quote endpoint distinct from the other buy_tok_* entries. It stops short of naming the generic sibling (buy_crypto_price) as an alternative for other assets.

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?

Cost, payment rails (Base or Solana), and the absence of account/API-key requirements give useful context for deciding whether to call, and 'Failed calls not charged' removes risk. However, there is no explicit when-to-use/when-not guidance and no differentiation from the very similar buy_crypto_price sibling or the other buy_tok_* tools.

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