Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MONEY

Paid. Defi.money (MONEY) 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/MONEY.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 a solid job: it discloses an up-front cost ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and critically that failed calls are not charged. It does not describe latency, rate limits, or response shape, which keeps it short of a 5.

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 the essence (the price, then price/terms, then endpoint URL) and it's only a few short fragments long. The telegraphic, period-separated style is dense but every sentence carries information; a smoother sentence flow would help readability.

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-argument, no-output-schema tool this is close to complete: the agent knows the subject, the cost, the payment rails, the failure policy, and the underlying URL. Only the exact response structure and whether the endpoint can be hit directly without payment are 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; the baseline applies. The description correctly signals that the token and payment medium are fixed, so the agent knows no arguments are required or accepted.

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 exact resource (Defi.money / MONEY) and the exact payload: live USD price, 24h change, market-cap rank. An agent knows precisely what it returns. It does not explicitly contrast itself with the many sibling price tools, but the baked-in token symbol makes the scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to pick this over alternatives such as buy_crypto_price or the other buy_tok_* tools — an agent must infer that this is the MONEY-specific endpoint. Payment terms and the payment chain are stated, but choosing between competing price tools is left entirely to inference.

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