Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OCT

Paid. Octra (OCT) 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/OCT.

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

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 behavioral burden and does so well: it discloses the paid cost ($0.05 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and the exact endpoint URL. The main omission is return format shape and any rate-limit or latency expectations.

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?

Six short sentences, front-loaded with the critical 'Paid.' signal, then resource, price, payment terms and endpoint. Nothing is redundant and every clause carries decision-relevant 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-param, no-output-schema tool, the description covers what is returned, what it costs, how to pay, and where it points. The only gap is the response envelope/format, which the description partially implies through the listed field names.

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 and there is no per-parameter meaning to add. The description usefully explains why no parameters exist (no account, no API key, token fixed in the name), which reinforces the zero-arg contract.

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 exact resource and verb: Octra (OCT) live USD price, 24h change and market-cap rank. It is unambiguous about what the tool fetches. It stops short of explicitly distinguishing itself from the generic sibling buy_crypto_price, leaving that differentiation to be inferred from the tool name.

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 context is implied by naming the specific token and its return fields, so an agent can infer this is the OCT price lookup. However, there is no explicit when-to-use or when-not-to-use guidance, and no pointer to buy_crypto_price as the general alternative for other assets.

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