Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WM

Paid. WrappedM by M0 (WM) 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/WM.

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

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 real work: it discloses that the call is paid ($0.05 USDC), which chains are accepted, that no account or API key is required, and that failed calls are not charged — the most important behavioral facts for a paid endpoint. It stops short of describing latency, response format, or failure modes, which keeps it out of the top band.

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?

Very compact and front-loaded: payment status first, then the data returned, then cost/chain, then access and billing caveats, then the URL. The telegraphic style ('Paid.', 'No account, no API key.') is slightly choppy but every clause carries distinct information and none is filler.

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, output-schema-less paid endpoint, the description supplies the returned fields, the price, the payment chains, access requirements, and a fallback billing guarantee — enough for an agent to decide and act. A note on output format or expected latency would make it complete.

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 further for the description to disambiguate about inputs; the baseline applies. The description instead pins down the fixed target (WM) and the fixed endpoint URL, which is the only input-adjacent detail that matters.

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 resource (WrappedM by M0 / WM) and states exactly what the call returns: live USD price, 24h change, market-cap rank. It is clear what the tool does, though with hundreds of near-identical buy_tok_*/buy_coin_* siblings it never states why an agent would pick buy_tok_WM over e.g. buy_crypto_price.

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 token name and the fields listed; there is no explicit statement of when to call this versus the generic buy_crypto_price or the buy_coin_WM-style siblings. The payment terms ('$0.05 USDC on Base or Solana') give practical context but are cost info, 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