Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDSM

Paid. Stable Mint USD (USDSM) 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/USDSM.

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

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?

No annotations are provided, so the description carries the full burden, and it does disclose substantive traits: this is a paid call with a stated price and payment chains, it requires no authentication, failures are not billed, and the backing URL is named. Missing only rate limits or retry semantics, which is a modest gap rather than a serious one.

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?

One dense line, front-loaded with the 'Paid.' flag so cost is known before anything else, then purpose, then pricing/auth terms, then URL. Telegraphic phrasing ('No account, no API key') is efficient rather than wasteful, though the cost and delivery details compete with the core purpose for attention.

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?

A no-parameter, no-output-schema price lookup is nearly fully covered: the description enumerates the returned fields (price, 24h change, market-cap rank) and states the payment and auth model, so an agent can call it without further inference. Only the response format and failure behavior beyond billing are left unstated.

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 the baseline is 4 and there is no parameter meaning for the description to add. The token is baked into the tool identity, which is the only 'input' an agent needs to reason about.

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 verb+resource: retrieves 'Stable Mint USD (USDSM) price' and names exactly what fields come back (live USD price, 24h change, market-cap rank). The token identity is clear, but the description never distinguishes this from the many adjacent siblings an agent could confuse it with (buy_crypto_price, buy_stable_usds, buy_tok_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?

Gives operational context (paid, $0.05 USDC on Base or Solana, no account or API key, failed calls not charged) which tells the agent the cost and prerequisites for calling. It does not say when to choose this over buy_crypto_price or a stablecoin-specific sibling, so selection guidance is only implied by the token 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