Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN3

Paid. τemplar (SN3) 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/SN3.

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

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 load and does so well: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and importantly that failed calls are not charged. It omits rate limits and whether the price data is cached or real-time per call.

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?

'Paid.' is front-loaded as a single word warning, followed by the data payload, the cost, the payment rails, the auth situation, the failure policy, and the endpoint. Every sentence adds a distinct operational fact with no filler.

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 paid endpoint with no output schema, the description covers what is returned, what it costs, how to pay, and what happens on failure — enough for an agent to decide and invoke correctly. Missing are the response envelope shape and how the payment handshake itself is performed.

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 nothing for the description to disambiguate and the baseline of 4 applies. The token identity is baked into the tool itself, which the description confirms by naming SN3 explicitly.

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 the specific resource (τemplar / SN3 price data) and enumerates the returned fields: live USD price, 24h change, market-cap rank. It also flags the tool as paid up front. It doesn't explicitly contrast with the generic buy_crypto_price sibling, which is the main thing keeping it off 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?

Usage is implied clearly enough — call this when you need SN3 pricing — and the payment terms tell the agent what it is committing to. But there is no statement of when to prefer this over buy_crypto_price or over per-token siblings, and no guidance on when a paid call is worth making.

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