Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MEW

Paid. cat in a dogs world (MEW) 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/MEW.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 a solid job: it declares the tool is paid, the exact cost and accepted payment chains, that no account or API key is needed, and that failed calls are not charged. That last point is a genuinely useful billing-behavior disclosure. It omits latency, rate limits, and failure-mode details.

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?

Telegraphic but front-loaded: purpose first, then return fields, then price/payment, then access terms, then endpoint. Every fragment carries information and nothing is repeated.

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 tool with no output schema, the description is nearly sufficient — it enumerates the returned fields (USD price, 24h change, market-cap rank), states the cost and payment options, and gives the endpoint URL. What is missing is response shape/units and any error or retry behavior beyond the no-charge-on-failure note.

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 no parameter meaning to add; the baseline of 4 applies. The description also avoids confusing the agent by not implying any hidden inputs.

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?

The description names a specific verb+resource: live USD price, 24h change and market-cap rank for 'cat in a dogs world (MEW)'. An agent can immediately tell this is the MEW price endpoint rather than a generic price tool. It does not, however, explicitly differentiate from the generic buy_crypto_price or the similarly-named buy_tok_MEY sibling, 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?

Usage is implied by the token-specific naming plus the payment disclosure ('$0.01 USDC on Base or Solana', 'No account, no API key'), which tells the agent the preconditions for calling. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to buy_crypto_price or buy_coin_MEW as an alternative.

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