Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GPS

Paid. GoPlus Security (GPS) 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/GPS.

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

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 behavioral burden and does well: it discloses cost, payment rails, absence of authentication, and that failed calls are free. It stops short of describing latency, caching/freshness of the 'live' price, or what a failure looks like, which would matter for 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?

Four compact clauses with the most decision-relevant fact ('Paid.') front-loaded, followed by payload, price, auth, and billing behavior, ending with the endpoint URL. No filler and nothing repeated from the schema.

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?

There is no output schema, so the description must convey the return value, and it does — price, 24h change, market-cap rank. Combined with cost, payment, auth, and failure-billing notes, an agent has what it needs to decide and call; only response format/error detail is absent.

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; there is nothing extra the description needs to explain about inputs. It correctly implies the symbol is fixed by the tool identity rather than passed in.

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 a specific resource and payload: GoPlus Security (GPS) live USD price, 24h change and market-cap rank. It is clear what the tool returns, but with hundreds of sibling buy_tok_* and buy_coin_* tools it never explains why the tok_ variant (this endpoint) is the right choice over the coin_ variant.

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?

It implies usage by disclosing that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and is not charged on failure — useful for deciding whether to call at all. However, it gives no explicit when-to-use or when-not-to-use guidance relative to the sibling price tools, leaving selection to be inferred from the name.

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