Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SAHARA

Paid. Sahara AI (SAHARA) 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/SAHARA.

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

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 burden and does well: it discloses a cost ($0.05 USDC on Base or Solana), that no credentials are required, and that failed calls are not charged. It stops short of stating the response format or rate limits, but the cost/failure policy is the material behavior for an agent deciding whether to spend.

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 what the agent gets, followed by what it costs and the access conditions. The raw endpoint URL is arguably noise for an agent, but the rest is dense and free of repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, everything an agent needs to call it and interpret the result is present: what fields come back, the price, the payment chains accepted, and the no-charge-on-failure guarantee.

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 schema requires nothing and the baseline is 4. The description correctly adds no parameter guidance and instead spends its words on pricing and output content.

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 a specific resource (Sahara AI SAHARA price) and enumerates what comes back: live USD price, 24h change, market-cap rank. The token symbol in the name does most of the differentiation from the hundreds of buy_tok_* siblings, and the description confirms the resource, but it never contrasts with the generic buy_crypto_price alternative.

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?

Gives access conditions (no account, no API key, failed calls not charged) but no explicit when-to-use or when-not guidance relative to buy_crypto_price or other token tools. The caller must infer selection from the tool name 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