Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GRAM

Paid. Gram (prev. Toncoin) (GRAM) 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/GRAM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 well: it discloses that the call is paid, the exact price ($0.01 USDC), the accepted payment chains (Base, Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, response format, and data freshness/staleness, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short fragments, front-loaded with "Paid." so the agent sees the cost gate first, then what is returned, then the price/chain/auth terms. Nothing is padding; the trailing URL is the only element an agent arguably cannot act on, and it is one clause.

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 lookup, the description covers cost, payment rails, auth requirements, failure billing, and the three returned fields — enough to call correctly. What is missing is the response format and whether the data is real-time versus delayed, which matters for a "live price" claim.

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 and there is no parameter meaning the description could add. The description correctly does not invent inputs, and the fixed symbol is baked into the tool name.

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?

"Gram (prev. Toncoin) (GRAM) price: live USD price, 24h change and market-cap rank" names a specific resource and enumerates exactly what is returned, so the agent knows the payload shape without a schema. It does not address the crowded buy_coin_*/buy_tok_* sibling space, so the agent gets no help disambiguating GRAM from the near-namesake buy_coin_TON.

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 by the noun phrase (this is the GRAM price lookup); there is no explicit "use this when" or "use X instead" statement, and no guidance on when buy_crypto_price or buy_coin_TON would be the better call. Commercial conditions (paid, no key, not charged on failure) are stated, which helps the agent decide to call at all, but routing guidance is absent.

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