Skip to main content
Glama

SouthPow crypto & market data

buy_tok_STONK

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full load, and it does disclose meaningful behavior: cost ($0.01 USDC), accepted chains (Base or Solana), no account/API key required, failed calls not charged, and the raw endpoint URL. It does not cover response format, latency, rate limits, or how the USDC payment is actually settled during a call, which for a paid tool is a real gap.

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?

Telegraphic but dense and front-loaded: paid status, data returned, price, chains, auth model, refund policy, URL — each fragment earns its place with no filler. The staccato style costs a little readability but wastes nothing.

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

Completeness3/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 it covers the essentials (what you get, what it costs, where it lives), but leaves the payment mechanism and response shape unstated — an agent knows the price $0.01 and chains but not how the charge is transacted or what the returned JSON looks like.

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 the baseline is 4; there is nothing for the description to disambiguate, and it correctly implies the token is baked into the tool rather than passed 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?

Names a specific resource (STONK token) and enumerates the exact payload: live USD price, 24h change, market-cap rank. The distinction from the ~1300 sibling buy_tok_<SYMBOL> tools is conveyed only by the token symbol embedded in the name and body, not by an explicit statement, so it is clear but not fully sibling-differentiated.

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?

The word "Paid" up front and the price/implicit cost signal that this is a paid fetch, which nudges usage, and it implies 'call this for STONK price data.' But it never says when to prefer this over the generic buy_crypto_price or the buy_coin_STONK sibling, and offers no exclusions or prerequisites beyond 'no account, no API key.'

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