Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GOOGLON

Paid. Alphabet Class A (Ondo Tokenized Stock) (GOOGLON) 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/GOOGLON.

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

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 supplied, the description carries the full burden and does disclose meaningful behavior: it is a paid call at $0.05 USDC, payable on Base or Solana, requires no account or API key, and failed calls are not charged. It omits rate limits, delivery/latency expectations, and whether payment is per-request signed, which keeps it below 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 a compact five-sentence block that front-loads the 'Paid.' flag, then the resource, then the returned fields, then cost and access terms. The sentences are short and each carries information, though the dollar/chain/URL tail reads as a run-on list rather than a structured ordering.

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 asset, the three returned metrics, the price, the payment chains, the lack of auth, the failure-charging policy, and even the endpoint URL. The main gap is the concrete response shape (field names, timestamp/currency precision), which an agent would still have to discover empirically.

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 beyond what the empty schema already shows; baseline 4 applies. The asset identity embedded in the name and description is the only 'parameter-like' information an agent needs.

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 specific asset (Alphabet Class A, Ondo Tokenized Stock, ticker GOOGLON) and the exact payload (live USD price, 24h change, market-cap rank), which lets an agent separate it from the GOOGLB/GOOGLC/GOOGLX siblings. It never uses an explicit verb like 'fetch' or 'returns', relying on the 'price: ...' fragment instead, so it stops just 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?

Purchase conditions are clear ($0.05 USDC on Base or Solana, no account or API key), which implies this is the paid route to GOOGLON price data. However, there is no explicit when-to-use guidance relative to alternatives such as buy_crypto_price or the other Google-token tools, and no stated exclusions.

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