Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN107

Paid. Tiger Alpha (SN107) 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/SN107.

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

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, the description carries the full behavioral burden and does well: it discloses that calls are paid ($0.01 USDC), the accepted chains (Base, Solana), that no account or API key is needed, and that failed calls are not charged — key facts for a paid endpoint. It omits rate limits, caching/staleness of the price, and expected response format.

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?

Extremely dense and front-loaded: the 'Paid.' lead and the price/payment terms come before the URL, and every clause (cost, chain, auth, failure billing, URL) carries unique information. No filler sentences.

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 annotations and no output schema, the description supplies the return fields (price, 24h change, cap rank), the cost, the payment rails, and the endpoint URL — enough for an agent to decide and invoke correctly. Missing only non-essential detail such as response encoding, refresh cadence, and whether payment is per-call via x402 headers.

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?

Zero input parameters, so the baseline is 4. The description correctly signals that the asset is baked into the endpoint rather than passed as an argument, which prevents an agent from hunting for a symbol parameter.

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 (Tiger Alpha, SN107) and the exact payload (live USD price, 24h change, market-cap rank), which resolves the cryptic tool name. It does not explicitly differentiate from other price-ish siblings such as buy_crypto_price or the neighboring buy_tok_SN* endpoints, so it stops short of a 5.

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?

Paid/price context implies when the tool is relevant, but there is no explicit statement of when to choose it over buy_crypto_price, buy_coin_*, or the other SN-index tools. Usage is inferable rather than stated.

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