Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SLC

Paid. Silencio (SLC) 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/SLC.

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

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 a solid job: it declares the tool is paid, gives the exact price and accepted chains, states the billing behavior on errors ('Failed calls not charged'), and removes auth concerns. It omits rate limits, data freshness/latency, and how the payment handshake actually works, which keeps it from a 5.

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?

A tight, front-loaded fragment set: 'Paid.' first, then what it returns, then cost/rails, then auth, then billing policy, then endpoint. Every clause carries information an agent needs before spending money. Slightly telegraphic construction rather than full sentences, but no wasted wording.

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-param, no-output-schema purchase tool, the description covers the facts that matter: what data comes back, what it costs, on which chains, no credentials required, and that failures are free. What is missing is freshness/update cadence and the mechanics of the USDC payment (e.g. a 402-style challenge), which would matter for an agent deciding whether to call it.

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 input schema has zero parameters, so the baseline is 4 and there is no parameter semantics to enrich. The ticker is hardcoded into the tool, and the description correctly signals the tool is call-free of arguments.

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 specific resource (Silencio / SLC token price) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is enough to separate it from the generic buy_crypto_price and the long buy_tok_* family by ticker. It stops short of a 5 because it never explicitly contrasts itself with the generic price tool.

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 rather than stated: an agent infers 'call this when you need the SLC spot price.' The payment and auth conditions ('no account, no API key', '$0.05 USDC on Base or Solana') give practical preconditions, but no explicit when-to-use / when-not-to-use guidance or named alternative is offered.

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