Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDS

Paid. USDS (USDS) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/USDS.

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

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 load and does well: it discloses the $0.05 USDC cost, the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, response format/units, and latency, so it stops 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?

Information is front-loaded ("Paid." then the payload then the commercial terms) and every clause carries a distinct fact. Minor waste in the redundant "USDS (USDS)" and the URL tail, which reads as marketing rather than invocation guidance.

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-output-schema, paid endpoint, the description covers cost, chain, auth model, failure billing, and the three returned metrics — enough to call it correctly. Missing only response shape/units and whether the price is point-in-time or delayed.

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 schema to document and no semantic gap for the description to fill. Baseline applies; the token identity is baked into the tool name and description.

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?

States a specific resource and payload: "USDS (USDS) price: live USD price, 24h change and market-cap rank." An agent can tell this returns a price snapshot for one named token rather than a generic feed, though it never explicitly contrasts itself with the sibling buy_crypto_price or buy_stable_usds.

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 is implied by the token name and payload list, but there is no explicit when-to-use or when-not-to-use guidance and no mention of the many alternative price tools in the sibling set. The payment and access notes help an agent decide it *can* call it, not whether it *should* versus a generic price endpoint.

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