Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TWT

Paid. Trust Wallet (TWT) 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/TWT.

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

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 that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. What it omits is price freshness/latency and rate limits for a paid endpoint, which would matter for repeated calls.

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?

A single dense sentence group with the paid flag front-loaded, followed by what is returned, cost, auth, failure policy and endpoint URL. No filler and nothing buried at the end that an agent lacks earlier.

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?

With no output schema and no annotations, the description still covers return contents, cost, auth requirements and failure charging, which is enough to invoke it confidently. The remaining gap is response shape/freshness detail, which would matter for an agent deciding whether to cache or re-call.

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 nothing for the description to disambiguate. The description correctly avoids inventing parameter semantics and instead spends its words on payment and return fields.

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 and verb: Trust Wallet (TWT) price, with the ticker disambiguated against the many similarly named siblings. It also enumerates what comes back (live USD price, 24h change, market-cap rank). It does not, however, distinguish itself from the generic buy_crypto_price or note that this is a paid per-token endpoint versus the free/other price tools.

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 data returned; there is no explicit 'use this when you need a spot quote for TWT' statement and no exclusion pointing at an alternative. The payment and no-account notes give practical context for whether an agent can call it, but not when it should choose this over a sibling.

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