Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SHARE

Paid. ShareX (SHARE) 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/SHARE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 load and does well: it discloses that the call is paid, the exact price ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits the mechanics of payment (how the USDC transfer is authorized) and any freshness or rate-limit characteristics, which is why it is not 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?

It is front-loaded with the most consequential fact ('Paid') and then the price, payload, payment rails, and endpoint, with no filler sentences. The trailing raw endpoint URL is the one element that does not clearly help an agent decide or invoke the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 data purchase tool, the definition covers what would otherwise be guesswork: the exact fields returned, the cost, the payment networks, and the billing behavior on failure. Nothing an agent needs in order to call it or to budget for it 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 and the schema is empty, so there is nothing to disambiguate and the baseline is 4. The description correctly implies the call is fully self-specified by the tool identity.

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 (ShareX / SHARE) and enumerates the payload: live USD price, 24h change, and market-cap rank. That is enough to separate it from the hundreds of sibling buy_tok_* tools, including a distinct buy_tok_SHX entry. The action verb is only implied ('price:' rather than 'returns'), which keeps this short of a 5.

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: an agent can infer it should call this when it needs SHARE spot price data. There is no explicit when-to-use framing, no alternative such as buy_crypto_price for generic quotes, and no statement of when not to call it (e.g. if the agent lacks USDC or a funded wallet).

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