Skip to main content
Glama

SouthPow crypto & market data

buy_cp_solana-ecosystem

Paid. Live crypto prices, solana ecosystem basket (SOL, JUP, JTO, PYTH, RAY, BONK, WIF, ORCA): USD median of Coinbase and Kraken, each source shown. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/solana-ecosystem.

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_cp_solana-ecosystem"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 burden and does so well: it discloses the commercial model ($0.01 USDC on Base or Solana), the friction profile (no account, no API key), the billing guarantee (failed calls not charged), and the data methodology (median of two named exchanges, each source shown). What it omits is the mechanics of how payment is settled and the response shape, though 'each source shown' hints at provenance fields.

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?

Front-loaded with 'Paid' so the cost signal lands first, then what you get, then the price and access terms, then the endpoint URL. Every clause is load-bearing—token list, median methodology, payment rail, and billing policy all affect the decision to call.

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 paid data endpoint with no output schema, the description supplies nearly everything an agent needs: cost, payment currency and chains, auth requirements, failure billing, and data provenance. The only real gap is that without an output schema the return shape (field names for the per-source prices) is only gestured at.

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 to fill. Baseline 4 applies; the description correctly spends no space explaining nonexistent inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (the Solana ecosystem basket) and enumerates its exact constituents (SOL, JUP, JTO, PYTH, RAY, BONK, WIF, ORCA), plus the aggregation method (USD median of Coinbase and Kraken). This makes it trivially distinguishable from the hundreds of sibling buy_coin_* single-asset tools and from buy_cp_majors or buy_cp_top10.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The enumerated basket implicitly tells the agent this is the one-call way to get all eight Solana tokens at once, versus calling buy_coin_SOL, buy_coin_JUP, buy_coin_JTO etc. individually. It also flags 'Paid' up front so the agent knows the cost gate before invoking. It stops short of explicitly stating 'use this instead of N single-coin calls' or any 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