Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ISLM

Paid. Islamic Coin (ISLM) 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/ISLM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the price ($0.01 USDC), accepted payment chains (Base or Solana), that no credentials are needed, and that failed calls are not charged — meaningful purchasing-behavior context. It omits how payment is actually settled (automatic x402-style charge vs. separate transaction) and any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Lead word 'Paid' front-loads the most decision-relevant fact, followed by payload, then price/rails, then trust signals, then the endpoint URL. Every phrase carries information and nothing is padded.

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 micro-purchase tool, the description covers cost, payment rails, auth requirements, failure policy, and the three returned fields. The only remaining gap an agent might want is the exact response shape or content type, which is minor here.

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 no parameter semantics to document; per the rubric this is the baseline 4. The description correctly implies nothing is configurable — the asset and endpoint are baked in.

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 asset ('Islamic Coin (ISLM)') and the exact data returned: live USD price, 24h change, and market-cap rank. That is far more than the bare name conveys, though it never explicitly contrasts itself with the many sibling per-token tools (buy_tok_*, buy_coin_*) beyond the embedded ticker.

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 only implied: an agent infers it is for fetching ISLM's spot price. It states access conditions (no account, no API key) but never says when to prefer this over alternatives such as buy_crypto_price or a general market-data sibling, and gives no exclusions.

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