Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN51

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

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

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, the description carries the full burden and does well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits and response shape/latency, which keeps it short of a 5 for a paid mutation-free endpoint.

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?

Five terse fragments, front-loaded with what the tool returns, then payment terms, then the endpoint. Nothing is padded and the paid nature is signalled in the first word, which is exactly the highest-value information to surface first.

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 the returned fields, the cost, the payment rails, and the failure policy, which is most of what an agent needs. It stops short of describing the response format or freshness guarantees, a minor gap given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema-full-coverage baseline of 4 would normally apply. However, there is nothing to clarify and the description adds no parameter-level meaning, making this a neutral rather than value-adding dimension.

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?

States a specific verb+resource: live USD price, 24h change and market-cap rank for the 'lium (SN51)' token. The ticker in the name and description cleanly separates it from other buy_tok_* entries, but the description never distinguishes it from adjacent price families such as buy_coin_* or buy_crypto_price, so an agent must infer the boundary from the naming convention alone.

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: the text makes clear it returns a spot price for one fixed token, so an agent can infer when it applies. There is no explicit guidance on when to choose this over buy_coin_* or buy_crypto_price, and no note about price freshness or cache window that would affect selection.

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