Skip to main content
Glama

SouthPow crypto & market data

buy_tok_M87

Paid. MESSIER (M87) 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/M87.

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

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 burden and does meaningful work: it discloses that calls are paid, the exact price and accepted chains, that failed calls are not charged, and that no credentials are required. It stops short of explaining the payment flow (how the $0.01 is settled by an agent with zero parameters) or any rate limiting.

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?

Four short sentences, each earning its place: cost flag first, then the payload, then settlement terms, then the endpoint. The staccato "Paid." lead is front-loading rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 what is returned and what it costs, which is the core. The unresolved gap is the mechanics of the payment itself — with no parameters and no annotations, an agent cannot tell how the USDC charge is triggered or what a paid response looks like.

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 no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly avoids inventing parameter behavior.

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?

"MESSIER (M87) price: live USD price, 24h change and market-cap rank" names a specific resource and the exact data returned, and the buy_ prefix plus the payment line make the transacted nature clear. It does not explicitly contrast itself with adjacent siblings such as buy_coin_* price tools, so sibling differentiation is left to the token 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 description establishes preconditions (paid, $0.01 USDC on Base or Solana, no account or API key, failures not charged), which implies when the tool is viable. It never states when to prefer this over another price source or what to do if the user lacks USDC, so usage is implied rather than directed.

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