Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MUON

Paid. Micron Technology (Ondo Tokenized Stock) (MUON) 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/MUON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full burden and does a good job: it discloses that the call costs $0.05 USDC, that payment can be made on Base or Solana, that no account or API key is required, and — most usefully — that failed calls are not charged. It stops short of stating rate limits, latency, or response shape beyond the named fields.

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?

It is short and front-loaded, leading with 'Paid.' so the cost signal is the first thing an agent sees, and every subsequent clause adds distinct information (data fields, price, chains, auth, failure billing). The raw URL at the end is telegraphic and the sentence fragments are terse, but nothing is padding.

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, no-output-schema tool this covers the things an agent actually needs: what data comes back, what it costs, on which chains, and that no credentials are required. It is not fully complete only because output format/pagination is unspecified and there is no guidance tying it to the broader catalog of sibling price tools.

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 declares zero parameters, so there is no parameter semantics to add beyond the baseline; the description correctly avoids inventing inputs. The asset is fixed by the tool itself, which is consistent with the empty input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource with its full identity — 'Micron Technology (Ondo Tokenized Stock) (MUON)' — which the bare tool name cannot convey, and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. An agent can tell this is the price feed for MUON specifically and not for any of the hundreds of other buy_tok_* siblings.

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 implies the usage context well by stating 'Paid. ... $0.05 USDC on Base or Solana. No account, no API key', so an agent knows the prerequisites and settlement path. What is missing is explicit routing: it never says when to prefer this over a sibling such as buy_crypto_price or buy_tok_ONDO, nor when the asset is irrelevant.

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