Skip to main content
Glama

SouthPow crypto & market data

buy_tok_YFSX

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

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

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 a solid job: it discloses that the call is paid, the exact cost and accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. The endpoint URL is included for reference. It stops short of describing rate limits, response format, or latency, so it is not fully transparent.

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?

Front-loaded with 'Paid.' so the agent sees the cost implication immediately, then packs the data returned, price, chains, auth requirements, and charging policy into three tight sentences. Every sentence earns its place; the only trivial noise is the redundant 'YFSX (YFSX)' label.

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 paid lookup with no output schema, the description covers what an agent needs: what it returns, what it costs, where to pay, and that it needs no credentials. The absence of any statement about the response payload structure or delivery mechanism is a minor remaining gap but does not block correct invocation.

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 semantics to explain and the baseline of 4 applies. The description correctly implies the token is baked into the endpoint rather than passed as an argument, which prevents an agent from hunting for a symbol parameter.

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 verb+resource: it returns the YFSX token's live USD price, 24h change, and market-cap rank. The token is named explicitly, which is what separates it from the hundreds of sibling buy_tok_* entries. It doesn't, however, explain how it differs from the broader buy_crypto_price or buy_coin_* families, leaving the agent to infer that this is the single-asset variant.

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 rather than stated: an agent can infer it should call this when it wants YFSX pricing. The description adds practical payment context ('Paid... $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged'), but never states when to prefer a sibling like buy_crypto_price or a bulk price tool instead, and offers no exclusion criteria.

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