Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SOFID

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description does real work: it discloses the price ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It does not cover rate limits, latency, or what a failure looks like, leaving the negative-path behavior only partially specified.

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 'Paid.' lead is front-loaded and the rest is telegraphic: what you get, what it costs, how you pay, and where it points. Every clause carries information, though the raw URL at the end is slightly out of place for an agent-facing description.

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 purchase tool with no output schema and no annotations, the description covers the return contents, the cost, the payment rails, and the failure-billing policy. The remaining gap is the response shape (field names, units, freshness), which an agent must discover by calling.

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 description to disambiguate; the schema is empty and complete. Baseline 4 applies, and nothing in the description misdescribes the call signature.

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 (SOFID / SoFiUSD) and enumerates exactly what the call returns: live USD price, 24h change, and market-cap rank. Paired with the tool name it is unambiguous against the many sibling buy_tok_* entries, though it never explicitly contrasts itself with near-neighbours like buy_crypto_price or buy_stable_sofid.

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 establishes the conditions of use indirectly by declaring the tool is paid and requires no account or API key, which tells an agent this is a pay-per-call lookup rather than a free endpoint. It gives no explicit when-to-use versus alternative price tools and no exclusions, so the agent must infer selection from the token symbol alone.

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