Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MUB

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

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

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, the description carries the full behavioral burden and does so well: it discloses the price, payment chains, cost, absence of authentication, and the important billing trait that failed calls are not charged. It also gives the endpoint URL. It stops short of describing response shape in detail or any rate limits, but covers the material behavior an agent needs.

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-loads the essential facts: paid status, asset, returned data, cost, payment options, auth, billing policy, and URL. It is compact and nearly every clause earns its place, though the telegraphic style and trailing raw URL are slightly less polished than possible.

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 price lookup, the description is nearly complete: it identifies the asset, enumerates the main returned fields, explains payment and billing, and notes that no credentials are needed. Minor gaps remain around exact response structure and freshness guarantees, but nothing critical to invocation 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 tool takes zero parameters, so there is no parameter semantics for the description to explain. The baseline of 4 applies; the description appropriately adds no param detail because none exists.

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?

States a specific verb and resource: live USD price, 24h change, and market-cap rank for Micron Technology tokenized stock (MUB). The ticker is named explicitly, so it is clearly distinguishable from the hundreds of sibling buy_tok_* tools that each target a different asset.

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?

Conveys that the call is paid ($0.01 USDC on Base or Solana) and requires no account or API key, which is useful context for deciding whether to call it. However, it never states when to use this versus alternatives such as buy_crypto_price or other token tools, leaving selection to be inferred from the ticker in the name.

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