Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GOOGLC

Paid. Alphabet (Coinbase Tokenized Stock) (GOOGLC) 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/GOOGLC.

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

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 supplied, the description carries the full burden and does well: 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. It stops short of explaining how payment is actually settled in-call (e.g. whether a 402 challenge is returned) or any rate limits, so it is strong but not complete.

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 agent sees the cost implication first, then the payload, then price and rails. The stacked parentheticals ('Alphabet (Coinbase Tokenized Stock) (GOOGLC)') are slightly dense, but every clause — price, rails, no-key, no-charge-on-failure, URL — carries information an agent needs.

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 tool, the description covers what is returned, what it costs, which chains settle payment, and the failure-charge policy. What remains unstated is the response shape and the mechanics of the payment handshake, which matters for an agent that must actually transact $0.05 USDC.

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 avoids inventing parameter discussion and instead spends its words on cost and return fields.

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?

States a specific resource (Alphabet/GOOGLC tokenized stock price) and the exact payload returned: live USD price, 24h change and market-cap rank. The ticker in the name plus the parenthetical identification makes it unambiguous against the many sibling buy_tok_* variants (GOOGLB, GOOGLON, GOOGLX, RGOOGL).

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: fetch a live price for this one asset. There is no guidance on when to prefer this over siblings like buy_crypto_price or buy_coin_* equivalents, and no statement of exclusions or preconditions beyond the payment model. The payment details are useful but they are cost information, not selection guidance.

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