Skip to main content
Glama

SouthPow crypto & market data

buy_tok_STEEM

Paid. Steem (STEEM) 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/STEEM.

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

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 at all, the description carries the full disclosure burden and does well: it declares the tool is paid, names the exact cost ($0.01 USDC), lists accepted payment chains (Base or Solana), removes auth friction (no account/API key), and states failed calls are not charged. It does not describe response format or rate limits, which is the remaining 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 'Paid.' then the payload, price, auth, failure policy, and endpoint — every clause conveys decision-relevant information. The telegraphic style ('Paid. Steem (STEEM) price: ...') is efficient but slightly clipped, which keeps it just under a 5.

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 price lookup with no output schema, the description supplies cost, payment rails, auth requirements, billing-on-failure policy, and a concrete endpoint URL, plus the fields returned. The only omission is a description of the actual response shape/units, which is modest given how simple the tool is.

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 and nothing in the description misrepresents the (empty) input contract. The embedded URL serves as the fixed endpoint rather than a configurable input, which is consistent with a no-arg call.

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+resource: live USD price, 24h change and market-cap rank for Steem (STEEM). The asset symbol in the name is echoed in the description, so an agent can distinguish it from the many sibling token tools. It does not explicitly contrast with close siblings such as buy_coin_STEEM or buy_crypto_price, so it stops short of a 5.

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 implies when to use it (fetch STEEM price data) and gives purchase prerequisites (no account, no API key), but never says when to prefer this over buy_coin_STEEM, buy_crypto_price, or other token endpoints in the same family. Usage is inferable from the payload description 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