Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USYC

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

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

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 supplied, the description carries the full disclosure burden and does a solid job: it discloses the paid model, the exact price and payment assets, the two supported chains, the absence of auth requirements, and failure-charge behavior. What it omits is the response shape/pagination and any rate-limit or latency expectations, 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?

It is a short, front-loaded block: purpose first, then payment terms, then the endpoint URL. Every clause carries information, though the run of terse fragments ('Paid.', 'No account, no API key.') reads as telegraphic rather than smoothly structured.

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, single-asset price lookup with no output schema, the description covers purpose, return fields, cost, chains, and auth prerequisites — enough for an agent to decide and call. The remaining gap is disambiguation from the adjacent USYC token and yield tools, which matters given the very large sibling set.

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 adds no parameter chatter, keeping the asset identity in the tool name and text rather than implying arguments that do not exist.

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 specific resource (Circle USYC / USYC) and enumerates the returned data points (live USD price, 24h change, market-cap rank), so an agent knows exactly what it fetches. It does not, however, distinguish itself from closely related siblings such as buy_yields_token_usyc or buy_yields_protocol_circle-usyc, which cover the same asset from a different angle.

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 conveys practical usage context indirectly — cost ($0.01 USDC), accepted chains (Base or Solana), no account or API key required, and no charge on failure — which tells an agent what it must have in place before calling. There is no explicit statement of when to prefer this over the sibling USYC tools, so selection between them is left to inference from the name.

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