Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SOMI

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

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

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 at all, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and gives the underlying endpoint. This is meaningful operational context an agent needs before spending money. It stops short of stating settlement mechanics, latency/freshness of the price, or failure behavior.

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 terse and front-loaded: payment status, then what the response contains, then cost/preconditions, then the URL. Every sentence adds information and none is filler. The telegraphic phrasing is slightly choppy but is appropriate for a machine-consumed definition.

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-value lookup with no output schema and no annotations, the description supplies the return fields, the price of the call, the payment rails, the authentication requirement, and the endpoint. That is nearly everything an agent needs to invoke it correctly; only freshness guarantees and the exact failure/refund path are 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 there is nothing for the description to disambiguate at the input level; the baseline of 4 applies. The token identity is baked into the tool itself, and the description confirms this by naming SOMI rather than implying a configurable symbol argument.

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 a specific resource (Somnia/SOMI) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. It is clear this is a single-asset price lookup. It does not, however, distinguish itself from the many sibling buy_coin_*/buy_tok_* price tools or from the generic buy_crypto_price, so an agent must infer the routing rule from the naming pattern alone.

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 context is only implied: the token is named, so 'call this to get SOMI price' is obvious. The paid-pricing and no-account details are useful preconditions, but there is no explicit when-to-use/when-not guidance, e.g. whether to prefer buy_crypto_price, buy_coin_SOMI, or this tool when several could answer the same question.

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