Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ANYONE

Paid. ANyONe Protocol (ANYONE) 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/ANYONE.

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

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 load and does well: it discloses the cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and the error policy (failed calls not charged). The only thing left implicit is the response shape and latency, which is minor for a fixed single-record lookup.

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?

Every clause earns its place and the critical facts are front-loaded: 'Paid' first, then the data returned, then price/rails/auth/refund policy, then the endpoint. No filler or repetition.

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, the description correctly enumerates the returned fields rather than leaving them unknown, and it covers the payment mechanics an agent or its operator needs before spending. What remains missing is only marginal: response format (JSON?) and freshness/caching of the 'live' price.

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 meaning to add; the schema is trivially complete. Nothing in the description conflicts with or under-specifies the empty input object.

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 resource precisely (ANYONE / ANyONe Protocol) and states exactly what the payload contains: live USD price, 24h change and market-cap rank. It is easy to separate from buy_tvl_* or buy_yields_* siblings, but it never distinguishes itself from the very closest alternative, buy_crypto_price, which appears to cover the same need.

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?

The scope of the call is implied by the token symbol in the name and by the listed return fields, so an agent can infer when it applies. However, there is no explicit statement of when to pick this over buy_crypto_price or over the buy_tok_*/buy_coin_* variants, and no exclusions are given.

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