Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FELY

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

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

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 behavioral burden and does well: it discloses the $0.01 USDC charge, accepted payment chains (Base or Solana), no account or API key requirement, and that failed calls are not billed. It omits any statement of data freshness, rate limits, or what a successful response body looks like, 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?

The definition is short and front-loaded: 'Paid' appears first, followed by what the data contains, the cost, and the endpoint URL. The telegraphic fragments ('$0.01 USDC on Base or Solana', 'URL …') are efficient, though the raw URL fragment slightly interrupts flow.

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 pricing tool, the description covers the essentials an agent needs to decide and invoke: the token, the data fields, the price, payment rails, and that failures are free. It could add response shape or freshness/latency, but nothing critical is missing.

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; the baseline for a 0-parameter tool applies. The description correctly avoids inventing parameters and instead spends its words on cost and output content.

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?

The description states a specific resource (Felysyum/FELY) and the exact payload: live USD price, 24h change, and market-cap rank. It distinguishes this per-token tool from the hundreds of sibling `buy_tok_*` entries by naming the symbol, but it never explicitly frames the family relationship (e.g., 'use the matching buy_tok_<SYMBOL> for other tokens').

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 'Paid' and the stated price, which lets an agent weigh cost before calling, but there is no explicit when-to-use or when-not guidance and no named alternative (e.g., a general price tool). The agent must infer that this is the right endpoint whenever FELY pricing is needed.

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