Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MSTRX

Paid. MicroStrategy xStock (MSTRX) 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/MSTRX.

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

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, the description carries the full burden and does a solid job: it discloses the paid model, exact price ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency and error/failure response behaviour, which keeps it short of a 5.

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-loaded with 'Paid.' and then the payload, which is exactly the order an agent needs. The telegraphic fragments pack a lot of decision-relevant detail into few words, though the clipped style borders on stenographic and the trailing bare URL adds little beyond what the tool already encodes.

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-param, no-output-schema tool, the description must say what comes back and what it costs; it does both, listing the three returned data points plus the payment and auth model. Only the absence of failure/response-format detail keeps it from being fully complete.

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 and the baseline of 4 applies. The description correctly implies the call is fully determined by the tool itself, with no symbol or currency argument to supply.

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 exact resource and scope: 'MicroStrategy xStock (MSTRX) price: live USD price, 24h change and market-cap rank.' That lets an agent separate it from the hundreds of buy_tok_* siblings without opening a schema. It does not distinguish MSTRX from near-neighbours such as buy_tok_MSTRB or buy_tok_MSTRON, and the 'buy_' prefix could momentarily suggest a token purchase rather than a paid price lookup.

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 'call this when you need the MSTRX spot price'. There is no explicit when-not or alternative routing (e.g. versus buy_crypto_price or the other MSTR variants). The cost and payment details do help the agent judge whether calling is worthwhile.

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