Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN68

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

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

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 behavioral burden and does a solid job: it declares the tool is paid, the exact price and accepted payment chains, that no credentials are needed, and — importantly — that failed calls are not charged. What remains undisclosed is the response shape, latency/freshness guarantees, and any rate limits, which matters for a metered endpoint.

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.' then the payload description, followed by cost, auth, and billing policy — all sentences earn their place for a metered endpoint. The raw endpoint URL is the one element of marginal value to a calling agent, but it is short and does not bloat the text.

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 and no parameters, so the burden is light, and the description covers cost, payment method, auth requirements, failure billing, and the returned fields. It is essentially complete; only the response format and freshness/rate characteristics are left unstated.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing input arguments and instead spends its words on the returned fields.

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 (NOVA, SN68) and enumerates the payload — live USD price, 24h change, market-cap rank — so an agent knows precisely what it returns. It stops short of explicitly contrasting itself with the many sibling price tools (buy_crypto_price, buy_coin_*, the other buy_tok_SN* endpoints), but the specificity of the resource makes the intent unambiguous.

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 implied: this is the SN68-specific price endpoint, and the '$0.01 USDC on Base or Solana / no account, no API key' lines give actionable prerequisites. However, there is no stated guidance about when to prefer this over buy_crypto_price or buy_coin_*, nor any exclusion for non-paid alternatives, so the agent must infer routing from the ticker alone.

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