Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDC

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

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

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 behavioral burden and does a solid job by disclosing that the tool is paid, the price, accepted payment chains, no authentication requirement, and that failed calls are not charged. It still lacks rate-limit, response-format, and payment-flow details, but covers the most important operational traits.

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 description is short, front-loaded with the paid nature and purpose, and avoids unnecessary filler. There is minor redundancy in 'USDC (USDC)' and the telegraphic style, but it remains easy to scan.

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 simple zero-parameter paid endpoint, the description covers what is returned, the cost, payment methods, authentication expectations, billing on failure, and the endpoint URL. It is nearly complete, though it could add response format or rate-limit context.

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 has zero parameters, so there is no schema-level parameter semantics to explain. The description correctly implies the USDC target is fixed by the tool/endpoint, which is sufficient for a no-parameter tool.

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 clearly states that this tool returns USDC's live USD price, 24h change, and market-cap rank. It is specific about the resource and returned data, but it does not explicitly distinguish this tool from adjacent siblings such as buy_stable_usdc or buy_yields_token_usdc.

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 gives useful invocation context: paid access, $0.01 cost, payment on Base or Solana, no account or API key, and no charge for failed calls. However, it does not state when to use this tool versus related price/stablecoin/yield siblings or when not to use it.

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