Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GIGGLE

Paid. Giggle Fund (GIGGLE) 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/GIGGLE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does unusually well: it discloses that the call is paid, the exact cost ($0.05 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It still omits rate limits, latency, and how payment is actually attached to the request.

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?

Dense and front-loaded: paid status first, then what data is returned, then cost/chains, then terms. Every sentence carries distinct information, though the raw endpoint URL is marginal for an MCP caller and could be dropped.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No input schema and no output schema, so the description must both define the payload and set expectations about billing. It does both: it names the three returned fields and states the charge, chains, auth-free access, and failure-billing policy. Little an agent needs to call this correctly is 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 for a no-param tool applies. The description correctly implies the token is fixed by the tool rather than passed as input.

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 verb and resource ('Giggle Fund (GIGGLE) price') and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. Against a sibling set of hundreds of near-identical buy_tok_* tools, the token symbol in the description is what an agent needs to disambiguate.

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: an agent infers 'call this to get GIGGLE price data.' There is no explicit when-to-use or when-not, and no routing guidance versus lookalike siblings such as buy_crypto_price or the buy_coin_* family. The payment/terms sentences are context, 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