Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ANSEM

Paid. The Black Bull (ANSEM) 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/ANSEM.

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

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 supplied, the description carries the full burden and does a solid job: it discloses the cost per call, accepted payment chains, the absence of auth, and the crucial billing rule that failed calls are not charged (which directly informs retry behavior). It omits rate limits, latency/freshness guarantees, and what tells an agent a call failed.

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 short fragments, front-loaded with the paid flag and the returned fields, then pricing, then auth, then billing, then endpoint. Every sentence adds a distinct operational fact with no repetition or 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 tool with no output schema and no annotations, the description covers what an agent most needs: what data comes back, what it costs, how to pay, and that failures are free. It leaves return-shape detail (field names, numeric formatting, units) and error signaling undocumented, which is a modest gap given no output schema exists to cover them.

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 for a parameterless schema applies. The asset being priced is fixed in the tool identity and repeated in the description, so no input semantics are needed.

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 the exact asset (ANSEM / The Black Bull) and enumerates the returned facts: live USD price, 24h change, market-cap rank. It is unmistakably a single-asset price feed rather than a general search or list tool. It stops short of a verb-led statement of what the tool does (e.g. 'Fetch the current ANSEM quote'), leaving the action implied by the title.

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?

Operational context is spelled out (paid, $0.05 USDC on Base or Solana, no account, no API key), which tells the agent this is a metered, credential-free call. However, there is no explicit when-to-use guidance and no reference to an alternative for ANSEM pricing or to the buy_coin_*/buy_tok_* siblings. Usage is implied by the price-fetch framing rather than stated.

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