Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BEAT

Paid. Audiera (BEAT) 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/BEAT.

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

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 behavioral burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC), accepted rails (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the backing endpoint URL. What it does not cover is rate limits, latency, or any error semantics beyond billing.

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?

The 'Paid.' prefix is front-loaded so cost is the first thing an agent sees, followed by the payload and payment mechanics. Every clause carries information, though the raw endpoint URL and repeated payment details make it slightly denser than necessary for a single-asset price lookup.

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, no-output-schema tool, the description covers the essentials: what is returned (price, 24h change, rank), what it costs, how to pay, and that failures are free. The main residual gap is how it relates to the massive buy_coin_*/buy_tok_* sibling set, which an agent cannot resolve from this text alone.

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 the baseline is 4; there is nothing for the description to disambiguate. It correctly avoids inventing parameters and instead spends its words on the asset and payment terms.

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 the specific asset (Audiera, ticker BEAT) and the exact payload: live USD price, 24h change and market-cap rank. An agent knows precisely what it retrieves. It does not distinguish itself from the many buy_coin_* and buy_tok_* siblings or from buy_crypto_price, so the resource is clear but the sibling boundary is not.

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 asset name and the 'Paid' marker; there is no explicit statement of when to choose this over buy_coin_BEAT-style siblings, buy_crypto_price, or the broader buy_tok_* family. The payment conditions are stated, but no alternatives or exclusions are offered.

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