Skip to main content
Glama

SouthPow crypto & market data

buy_tok_THETA

Paid. Theta Network (THETA) 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/THETA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 it does add real value: cost ($0.05 USDC on Base or Solana), no account or API key, failed calls not charged, and the endpoint URL. It omits freshness/latency (is the price live-updating or cached), rate limits, and the response shape beyond the three named fields.

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?

Front-loaded with "Paid." so the agent sees the cost gate immediately, then what it returns, then payment mechanics. Every sentence carries distinct decision-relevant information with no padding.

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 no-parameter, no-output-schema paid endpoint, the description covers cost, payment rails, auth requirements, failure billing, and the fields returned — enough to decide and call correctly. Missing freshness and exact response structure keeps it short of a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters (schema coverage 100% trivially), so there is nothing for the description to disambiguate. The baseline for a no-parameter tool applies; the token identity is fixed by the tool name rather than a parameter.

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 resource precisely ("Theta Network (THETA) price") and enumerates the returned data (live USD price, 24h change, market-cap rank), so an agent knows exactly what it buys. It does not, however, distinguish this endpoint from adjacent siblings such as buy_crypto_price or the buy_coin_* family that likely serve similar 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 it should call this when it needs THETA spot pricing. There is no explicit when-to-use/when-not-to-use guidance and no pointer to alternatives like a generic price tool, though the payment prerequisite is spelled out.

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