Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LIGHT

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

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

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 ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. It stops short of latency, rate limits, or freshness/caching behavior for 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?

Information is front-loaded (payment status first, then payload, then pricing/auth terms, then URL) and is telegraphic with little waste. The leading 'Paid.' is slightly redundant with the later '$0.01 USDC' line, a minor duplication rather than bloat.

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 price tool, the description covers the essentials: what is returned, what it costs, how to pay, that no credentials are needed, and failure billing. An agent can invoke it correctly from this text alone; only freshness/rate-limit details are missing.

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 for the description to add or omit. Schema coverage is moot at 0 properties.

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 the exact asset (Bitlight, LIGHT) and enumerates what is returned: live USD price, 24h change and market-cap rank. That is a specific resource plus concrete payload, so it is distinguishable from the hundreds of sibling buy_tok_* tools by ticker. It does not, however, route the agent against adjacent generic tools like buy_crypto_price or the buy_coin_* family.

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: an agent can infer it should call this when it wants the LIGHT price. There is no explicit when-to-use or when-not-to-use statement, and no comparison to buy_crypto_price or buy_coin_LIGHT-style alternatives, which matters given the very large sibling set.

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