Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MSTRB

Paid. Strategy (bStocks Tokenized Stock) (MSTRB) 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/MSTRB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 full behavioral burden and does it well: it discloses that the call is paid ($0.01 USDC), payable on Base or Solana, requires no account or API key, and that failed calls are not charged. It omits response shape and latency, but the cost/failure/permission profile — the highest-risk facts for a paid endpoint — are all stated.

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?

Short and front-loaded: the paid marker and the returned fields come first, followed by price/payment terms and the endpoint URL. The fragmentary style ('Paid.' as a standalone sentence) is slightly choppy but wastes no words.

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 paid price lookup with no output schema, the description covers what is returned, what it costs, how to pay, auth requirements, failure billing and the endpoint. Only the exact response format and freshness/latency of the quote 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 the schema has nothing to document and no compensation is required. The description correctly implies no inputs are needed by naming a fixed URL and fixed ticker.

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 — Strategy (bStocks Tokenized Stock) MSTRB — and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. It does not, however, distinguish MSTRB from near-identical sibling variants such as buy_tok_MSTRON, buy_tok_MSTRX or buy_tok_RMSTR, which an agent would need in order to pick the right ticker.

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?

Usage is only implied: the leading 'Paid' marker plus the price-ticker name signals a per-symbol paid quote lookup. There is no explicit when-to-use or when-not statement and no comparison against the many other tok_ price endpoints, so the agent must infer selection from the ticker suffix.

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