Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TA

Paid. Trusta AI (TA) 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/TA.

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

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, the description carries the full burden and does well: it discloses cost ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying URL. It omits rate limits, latency, and caching behavior, which keeps it short of a 5.

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?

Front-loaded with the single most decision-relevant fact ('Paid.') followed by payload, price, payment rails, and endpoint. Nearly every clause earns its place, though the bare URL at the end is more operational metadata than agent-facing guidance.

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, no-output-schema quote endpoint, the description covers what is returned (price, 24h change, rank), what it costs, and how payment works. Nothing an agent needs in order to decide and call is missing; only secondary details like response shape and rate limits are absent.

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 baseline is 4. The description correctly implies the call needs no inputs by noting no account or API key is required, and adds nothing misleading about parameters.

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 the specific resource and payload precisely: 'Trusta AI (TA) price: live USD price, 24h change and market-cap rank.' The ticker plus project name distinguishes it from the hundreds of other buy_tok_* siblings. It does not explain how buy_tok_* differs from the parallel buy_coin_* family, so the sibling differentiation is only partial.

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 (call this to get the TA price) and payment mechanics are spelled out, but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives such as a broader crypto-price endpoint. An agent must infer that this is the single-token quote tool.

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