Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MTL

Paid. Metal DAO (MTL) 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/MTL.

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

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 full burden and does well: it discloses the pricing model ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits and any latency/freshness caveats, so it is strong but not exhaustive.

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?

Terse and front-loaded: the paid status comes first, then the payload, then cost, access, and billing semantics. The telegraphic fragments ('Paid.', 'No account, no API key.') are efficient for this catalogue, though slightly clipped prose costs a point.

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?

Given no output schema, no annotations, and no parameters, the description covers what an agent needs to call it: the returned fields, the cost and payment chains, the no-auth requirement, and the endpoint. Only the exact response shape (field names, units, update cadence) is left unstated.

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 beyond confirming the call is self-contained. It does that implicitly by naming the specific asset in the URL path rather than describing an input field.

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 resource (Metal DAO / MTL) and exactly what it returns: live USD price, 24h change, and market-cap rank. An agent can tell what it fetches. It does not, however, explain how it relates to the parallel buy_coin_* family or name a sibling to prefer, which keeps it below 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?

Usage is implied (fetch MTL's spot price and 24h stats) but there is no explicit when-to-use/when-not guidance and no named alternative among the many sibling price tools. The payment and access notes provide practical calling context but are not selection guidance.

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