Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN41

Paid. Sportstensor (SN41) 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/SN41.

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

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 well: it discloses that the call is paid ($0.05 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of describing rate limits, latency, or the response shape beyond naming the three fields.

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?

It is front-loaded with the paid status and purpose, then pricing, then access terms, with no filler sentences. The trailing raw endpoint URL is the only element that arguably does not earn its place for an agent invoking the tool through MCP.

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 tool, the description must convey what comes back, and it does by listing price, 24h change, and market-cap rank, plus full cost and access terms. Minor gaps remain around error/failure semantics beyond the no-charge guarantee and the exact response structure.

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 description correctly implies the token is fixed by the tool name rather than passed as an argument.

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 (Sportstensor / SN41) and enumerates the payload: live USD price, 24h change, and market-cap rank. It is clearly distinguishable from the hundreds of sibling buy_tok_* tools by the SN41 token identifier, though it never explicitly says 'use this instead of buy_crypto_price' for the same data.

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 only implied: an agent infers you call this to obtain SN41 pricing. There is no explicit statement of when to prefer this over a sibling like buy_crypto_price or buy_tok_TAO, nor any exclusion of cases where it would be the wrong choice.

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