Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GNOT

Paid. Gno.land (GNOT) 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/GNOT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/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 so well: it discloses the cost ($0.05 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Those are exactly the facts an agent needs before committing to a paid call.

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?

It is front-loaded with 'Paid.', then the data fields, then price and billing terms, then the endpoint. Every fragment carries distinct information — cost, rails, auth, failure policy, URL — with no repetition of the tool name or filler prose.

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?

With no output schema, the description must convey the return content, and it lists the three data points returned, plus pricing and payment mechanics. What is missing is only secondary: response format, data freshness/latency, and any rate limits, none of which block a correct call.

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 no parameter meaning to convey and the baseline of 4 applies. Nothing in the description is needed to explain inputs, and the single fixed-token scope is clear from the name and text.

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?

The description names the exact resource (Gno.land / GNOT) and the exact payload it returns: live USD price, 24h change, and market-cap rank. In a family of hundreds of near-identical buy_tok_* siblings, this pins down the token and the metrics, so an agent can select it without opening anything else.

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: 'Paid' plus the per-token framing tell the agent this is a single-token purchase, and the token name constrains when it applies. There is no explicit statement of when to prefer it over the generic buy_crypto_price tool or the buy_coin_* variants, and no when-not 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