Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TEMPLE

Paid. TempleDAO (TEMPLE) 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/TEMPLE.

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

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 supplied, the description carries the full behavioral load and does well: it discloses the cost ($0.01 USDC), the payable chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It stops short of describing response shape, latency, or pricing changes, but the commercial and auth behavior is unusually well covered.

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?

Three terse sentences plus a URL, with the core payload front-loaded before the commercial terms. Telegraphic style ('Paid.', '$0.01 USDC on Base or Solana.') is efficient, though the fragmentary phrasing reads slightly like ad copy rather than documentation.

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 price lookup, the definition covers what is returned, what it costs, how payment works, and where it is served — enough for an agent to decide and invoke. The only gap is that the response field layout is unstated and there is no output schema to fall back on.

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 imposes no semantic burden and the description correctly adds none. The asset is bound into the tool itself, which is the right design and needs no further parameter explanation.

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 asset (TempleDAO / TEMPLE) and the exact payload: live USD price, 24h change, market-cap rank. An agent can tell this is a single-token spot-price endpoint without opening anything else. It lacks an explicit statement that sibling buy_tok_* tools cover other tokens, so differentiation is by name rather than prose.

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 by the asset-specific name plus the stated price payload, and the 'Paid... No account, no API key' framing tells the agent this is a metered purchase. However, there is no explicit 'use this when you need TEMPLE price data' clause and no pointer to alternatives (e.g. buy_crypto_price or buy_tok_* 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