Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GOOGLX

Paid. Alphabet xStock (GOOGLX) 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/GOOGLX.

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

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 load and does well: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — the failure/billing semantics are the key risk here and they are stated. It omits the payment mechanism itself (how the agent settles USDC) and any latency or rate-limit behavior.

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.' so the cost signal lands first, then payload, then price/rails, then billing guarantee, then a source URL. Dense and waste-free, though the telegraphic fragment style packs several distinct claims into one run-on chain.

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 fetch with no output schema and no annotations, the agent learns what data comes back, what it costs, how to pay, that no auth is required, and that failures are free. The main residual gap is the payment handshake procedure, which is not described.

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; baseline 4 applies. The description usefully clarifies that the ticker is fixed per tool rather than supplied as an argument.

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 a specific verb ('price') and resource ('Alphabet xStock (GOOGLX)'), and enumerates the exact data returned: live USD price, 24h change, market-cap rank. It does not distinguish GOOGLX from the many near-identical siblings (buy_tok_GOOGLB, buy_tok_GOOGLC, buy_tok_GOOGLON, buy_tok_RGOOGL), so an agent must rely on the ticker suffix in the name alone.

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 by the ticker in the name rather than stated; there is no explicit 'use this when…' or 'use buy_crypto_price instead for…' guidance. The cost, payment rails, and no-account/no-API-key conditions give useful context for deciding to call, but nothing excludes or routes between the sibling GOOGL variants.

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