Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SANC

Paid. Sanctum (SANC) 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/SANC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/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 disclose valuable traits: it is paid, costs $0.01 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. It omits rate limits, data freshness/caching, and the shape of a successful response, which matters for an agent deciding to spend money.

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?

Five short sentences, front-loaded with the critical 'Paid.' signal and the concrete price before the endpoint details. Nothing is padded; each clause (cost, chain, auth, error policy, URL) contributes actionable information.

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 lookup, the description covers what is returned, the cost, the payment rails, auth requirements, and the failure-charge policy. Only return-format and freshness details are absent, and with no output schema those are a minor residual gap rather than a blocker.

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. The description cannot add parameter meaning, but it correctly implies the asset is fixed by the endpoint and requires no input from the caller.

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 and asset ('Sanctum (SANC) price') and enumerates the returned fields (live USD price, 24h change, market-cap rank), so an agent knows exactly what data this yields. It does not explicitly distinguish itself from the generic buy_crypto_price or the parallel buy_coin_* family, which is the main gap.

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 paywalled per-asset price lookup for SANC — but there is no explicit when-to-use versus buy_crypto_price or a broad market tool, and no statement of when this is preferable to a free endpoint. The payment context gives a reason to hesitate, yet no guidance on whether cheaper alternatives exist.

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