Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GOOGLB

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

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

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 provided, the description carries the burden and does well: it discloses that the call is paid, the exact price and accepted assets/chains (USDC on Base or Solana), that there is no auth, that failed calls are not charged, and it gives the endpoint. It omits things like rate limits, latency, or what a failure looks like, but the core commercial and safety profile is disclosed.

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?

Sentence one leads with the paid flag, then the resource and returned fields; subsequent sentences cover cost, auth, failure policy, and endpoint. It is dense and front-loaded with no filler, though the raw URL adds little for an agent that already knows the tool.

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-annotation, no-output-schema tool, the description covers all the decision-relevant facts: what is returned, what it costs, on which chains, that no auth is needed, and the failure billing policy. Only the sibling-differentiation and output-format details are 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, so there is nothing for the description to disambiguate; the baseline of 4 applies. The endpoint URL and fixed asset identity reinforce that no input is needed.

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 resource (Alphabet bStocks tokenized stock, GOOGLB) and enumerates the exact payload: live USD price, 24h change, and market-cap rank. It does not differentiate itself from the many closely named sibling variants (buy_tok_GOOGLC, buy_tok_GOOGLON, buy_tok_GOOGLX, buy_tok_RGOOGL), which is the main gap for a tool whose name alone is ambiguous.

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: pay $0.05 to get GOOGLB pricing, with no account or API key required. There is no explicit statement of when to prefer this over the sibling Google-token price tools, and no prerequisites or exclusions are stated.

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