Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GAL

Paid. GAL (migrated to Gravity - G) (GAL) 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/GAL.

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

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 well: it declares the tool is paid, prices it at $0.05 USDC, names the accepted payment chains (Base or Solana), states no account or API key is required, and specifies that failed calls are not charged — the key risk-relevant fact for a pay-per-call endpoint. It omits rate limits and how payment is actually transacted, which keeps it from 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?

Front-loaded with the single most important fact ('Paid.') followed by scope, price, payment rails, and endpoint in a compact run of short clauses. Minor waste in the redundant 'GAL (migrated to Gravity - G) (GAL)' construction, but every other clause earns its place.

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 paid lookup, the description covers what is returned (price, 24h change, market-cap rank), what it costs, how to pay, and where the endpoint lives. The only real gap is the absence of any rate-limit or latency expectation and the missing pointer to buy_tok_G as the post-migration alternative.

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 is 4. The description correctly implies the call is fully self-contained (the token is baked into the name), so an agent knows no argument 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 the exact resource (GAL) and enumerates the returned data points: live USD price, 24h change, and market-cap rank. It also flags the token migration to Gravity (G), which helps an agent disambiguate from the sibling buy_tok_G. It stops short of positioning itself against generic siblings like buy_crypto_price or the buy_coin_* family.

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 can infer this is the tool for GAL's spot price, and the migration note hints that buy_tok_G may be the successor. There is no explicit when-to-use / when-not-to-use statement and no named alternative for comparable price lookups (e.g., buy_crypto_price or buy_coin_* variants).

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