Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DENIM

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

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

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 at all, the description carries the full burden and does well: it discloses the price ($0.05 USDC), the accepted payment rails (Base or Solana), that no authentication is needed, and that failed calls are not charged. It stops short of describing rate limits, retry semantics, or how the payment is actually negotiated against the listed URL.

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?

Five short fragments, front-loaded with 'Paid.' so the cost model is the first thing the agent learns. Nothing is padded and each clause contributes a distinct fact (data, price, rails, auth, failure policy).

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, output-schema-less paid lookup, the description supplies the payload contents, the payment cost and chains, and the failure-billing policy. Only marginal items such as response format or error signaling are absent, which is acceptable at this complexity.

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 no parameter semantics to explain beyond what the empty schema already shows; the baseline for a no-arg tool applies.

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?

Names the specific resource (DENIM live USD price) and enumerates exactly what is returned: 24h change and market-cap rank. It is clear this is the DENIM-specific entry among the per-asset buy_tok_* siblings, though it never explicitly contrasts itself with the generic crypto_price siblings.

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 by the asset name and the listed outputs; there is no explicit 'use this when...' or guidance on when to prefer it over buy_crypto_price or buy_coin_* alternatives. The 'No account, no API key' line gives a prerequisite, which helps, but selection guidance is missing.

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