Skip to main content
Glama

SouthPow crypto & market data

buy_tok_METAL

Paid. Metal Blockchain (METAL) 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/METAL.

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

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 burden and does most of it well: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It omits any statement about response shape, latency, or how payment is actually settled.

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.' followed by the payload, price, access terms, and URL — every element earns its place. The phrasing is telegraphic to the point that '$0.05 USDC on Base or Solana' takes a moment to parse as payment terms rather than as the quoted asset price.

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 three things an agent needs to commit: what data comes back, what it costs, and that no credentialing is required. The remaining gap is response format and whether repeated calls or retries incur additional charges.

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. The description correctly adds no parameter prose and instead spends its words on cost and access conditions, which is the right allocation for a no-arg endpoint.

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 the resource and exact payload: 'Metal Blockchain (METAL) price: live USD price, 24h change and market-cap rank.' The ticker in the tool name plus the expansion to 'Metal Blockchain' distinguishes it from the hundreds of sibling token endpoints. It stops short of saying how it relates to adjacent siblings like buy_crypto_price or buy_coin_* lookups.

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 payload description (an agent wanting METAL price data). There is no explicit statement of when to prefer this over buy_crypto_price or a buy_coin_* endpoint, and no 'when not to use' guidance, though the 'Paid.' opener signals this is a purchasable call rather than a free lookup.

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