Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MSUSD

Paid. Metronome Synth USD (MSUSD) 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/MSUSD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 discloses the crucial behaviors: it is a paid call, costs $0.05 USDC on Base or Solana, requires no auth, and failed calls are not charged. That failure/charging policy is exactly the kind of non-obvious behavior an agent needs before invoking. It stops short of describing latency or response shape.

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 payment flag and the returned fields, then price, auth, and failure policy, then URL. Six short fragments, no filler. The leading 'Paid.' is terse but functional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param tool with no output schema, the description covers cost, chains, auth, failure policy, and endpoint, but leaves the return structure (field names, units, freshness) underspecified beyond a prose list. Adequate but not fully self-contained for an agent that must parse the response.

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 implies there is nothing to supply and instead documents the endpoint URL, which is the only 'input' an agent might wonder about.

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 the specific resource (Metronome Synth USD) and the exact fields returned: live USD price, 24h change, and market-cap rank. It does not distinguish this from near-neighbors like buy_tok_MUSD (a differently named token) or buy_crypto_price, so an agent must rely on the name prefix to disambiguate.

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?

It states access conditions ('No account, no API key') but gives no when-to-use guidance or exclusions relative to the many sibling price tools. An agent gets no signal about when this endpoint is preferable to buy_crypto_price or the buy_tok_* family.

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