Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MSTRON

Paid. MicroStrategy (Ondo Tokenized Stock) (MSTRON) 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/MSTRON.

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

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 a solid job: it discloses that the call is paid ($0.05 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged, which is exactly the billing and auth context an agent needs before invoking. It stops short of disclosing rate limits, latency, or the response shape (e.g. units, timestamp), so it is not exhaustive.

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 a compact, front-loaded block: payment flag first, then resource and payload, then cost/auth/failure policy, then endpoint. Every clause carries information. The raw URL is arguably operational trivia rather than decision-relevant content, which keeps it just below maximal concision.

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 endpoint, the description covers the essentials: what asset, what fields come back, what it costs, and how payment/auth works. Missing only minor detail an agent might want, such as freshness guarantees or the exact response structure, which the absence of an output schema makes slightly more valuable.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies the asset is fixed by the endpoint rather than passed in, which prevents an agent from looking for a ticker argument.

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 names a specific resource (MicroStrategy / Ondo Tokenized Stock, ticker MSTRON) and states exactly what is returned: live USD price, 24h change and market-cap rank. Against a sibling set of hundreds of ticker-specific buy_tok_* tools, the ticker plus the stated payload is enough for an agent to know precisely which asset and which data this call yields.

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 implied rather than stated: an agent infers this is the spot-price lookup for MSTRON. There is no explicit when-to-use or when-not-to-use guidance, and no routing to plausible alternatives such as buy_crypto_price for general pricing or other buy_tok_/buy_coin_ siblings for related assets or the underlying stock.

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