Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FOLKS

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

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing are return shape and data freshness/latency, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five tight sentences: what it returns, the price, the payment rails, the auth-free nature, the refund policy, then the URL. Payment and price are front-loaded with the tool name, and no sentence is filler.

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-annotations, no-output-schema tool, the description covers the essential unknowns: cost, payment method, auth requirement, failure billing, and the returned fields. It would be complete at 5 if it said whether the price is real-time versus delayed and roughly what the response looks like.

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 and the baseline of 4 applies. The description correctly implies no inputs are needed by supplying the asset and endpoint URL inline.

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 names the exact asset (FOLKS) and enumerates the returned fields: live USD price, 24h change, and market-cap rank, so an agent knows precisely what it gets. It falls short of 5 because it never explains how this differs from the many sibling price tools (buy_coin_*, buy_crypto_price, buy_tok_* variants) beyond the paid/free distinction implied by 'Paid.'

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?

It clearly frames the context in which this tool applies (a paid, accountless per-asset quote at $0.01 per call) and implies the caller is paying for a live price snapshot. However, there is no explicit when-to-use or when-not-to-use guidance, and no named alternative for callers who want a free or batch price source among the hundreds of sibling tools.

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