Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GOHOME

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

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

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 discloses that the call is paid, the exact price and accepted payment chains, that no account or API key is required, and that failed calls are not charged. The remaining gap is that it says nothing about latency, rate limits, or caching of the quoted price.

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 'Paid.' followed by what is returned, then cost, then terms, then the endpoint — a sensible ordering with no filler sentences. Minor waste in the redundant 'GOHOME (GOHOME)' pairing, but nothing that harms comprehension.

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 paid lookup with no output schema, the description covers cost, payment rails, auth requirements, failure billing, and the three fields returned, which is close to everything an agent needs before calling. It could only be stronger by specifying the response shape or freshness of the 'live' quote.

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 beyond confirming the asset is fixed (GOHOME). Baseline for a parameterless schema applies; the symbol baked into the tool name is reinforced by the description's 'GOHOME (GOHOME)'.

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 states a concrete resource and payload: 'GOHOME (GOHOME) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what comes back. It does not, however, explain how this differs from the large buy_coin_* / buy_crypto_price families that return similar price data, so it is clear but not 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?

Usage conditions are covered in the commercial sense: 'Paid', '$0.05 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged' tells the agent what it costs and that no credentials are needed. There is no guidance on when to pick this over buy_crypto_price or the buy_coin_* variants for the same asset, which is the main decision an agent faces here.

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