Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SECZ

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

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

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 the price, accepted payment chains, absence of auth requirements, the failure-charging policy, and the underlying endpoint URL. It stops short of describing response shape or latency, but the core behavioral contract for a paid call is covered.

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?

Six short clauses, cost front-loaded with 'Paid.', then payload, then payment mechanics, then refund policy, then URL. No sentence is redundant and an agent can extract the decision-relevant facts in one pass.

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 lookup, the description supplies both what is returned and the full cost/auth/failure contract. Only the response format and freshness/latency guarantees are unstated, which is a minor gap at this complexity level.

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 nothing for the description to disambiguate beyond confirming no arguments are needed. Baseline of 4 applies for a parameterless tool.

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 exact asset (Securitize / SECZ) and enumerates the returned data points: live USD price, 24h change, market-cap rank. That is enough to distinguish it from generic siblings like buy_crypto_price, though it relies on the symbol in the tool name rather than stating a verb such as 'fetch' to differentiate from the many buy_coin_* variants.

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 context is implied by the payment terms ('$0.01 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged'), which tells an agent this is a cheap pay-per-call endpoint. However, there is no explicit when-to-use guidance and no routing statement pointing to buy_crypto_price or a buy_coin_* sibling for broader queries.

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