Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ARMUSDCS

Paid. Wintermute USDC Select (ARMUSDCS) 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/ARMUSDCS.

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

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 provided, the description carries the full burden and does reasonably well: it discloses the paid nature, exact price ($0.01 USDC), accepted payment chains (Base or Solana), absence of auth requirements, and a failure-billing policy. What it omits is rate limiting, data freshness/caching, and the shape of the response, which matter for a paid data call.

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?

Roughly four short sentences, each carrying distinct information: cost marker first, then what data is returned, then payment/auth terms, then the endpoint. Nothing is repeated and the paid status is front-loaded where an agent will see it immediately.

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?

There is no output schema, so the description must indicate return values, and it does list the three data points delivered. Combined with the payment and failure-billing terms, an agent has enough to decide and invoke. It could be stronger with a note on response format or data latency, but nothing essential to calling it correctly is missing.

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 schema has zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The statement that no account or API key is required usefully confirms the tool is callable with an empty argument object.

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 ('Wintermute USDC Select (ARMUSDCS) price') and enumerates what comes back: live USD price, 24h change, and market-cap rank. That is a concrete verb+resource statement an agent can act on. It stops short of explicitly differentiating itself from the hundreds of sibling buy_tok_* tools, relying on the ticker in the name to do that work.

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?

It gives access and cost context ('No account, no API key', '$0.01 USDC on Base or Solana', 'Failed calls not charged') that tells an agent this is callable without setup. However, it never states when to choose this over an alternative such as buy_crypto_price or buy_tok_USDC, and there are no exclusions or prerequisites spelled out beyond payment.

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