Skip to main content
Glama

SouthPow crypto & market data

buy_pm_solana

Paid. Live Polymarket odds for 'solana' markets, sorted by 24h volume: odds per outcome, volume, liquidity, end date, link. $0.05 USDC on Base. No account, no API key. URL https://southpow.media/v1/polymarket/solana.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

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 load and does a solid job: it discloses that the call is paid, the exact price ($0.05 USDC), the settlement chain (Base), and that no account or API key is required — all things an agent cannot infer from the schema. Gaps remain: it never explains how payment is actually executed (e.g. an x402-style handshake), what happens if payment fails, or whether rate limits exist.

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?

Telegraphic but flawless in ordering: 'Paid' leads with the most consequential fact, then scope, then return fields, then price and access requirements, then the endpoint URL. Every fragment earns its place and nothing is repeated from structured fields.

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 one-optional-param read tool with no output schema, the description is close to self-sufficient: scope, sort order, returned fields, cost, chain, and auth requirements are all covered. The remaining hole is the payment/authorization flow — an agent still does not know what it must do to satisfy the $0.05 charge beyond calling the URL.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single optional 'limit' param is already documented as 'Markets, 1-50 (default 10)', so the schema does the heavy lifting. The description adds no meaning about the parameter, but it does add return-shape meaning — odds per outcome, volume, liquidity, end date, link — plus the 24h-volume sort order, which is not in the schema. Baseline 3 applies.

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 precise resource and scope: live Polymarket odds restricted to 'solana' markets, sorted by 24h volume. That distinguishes it from the many sibling topic tools (buy_pm_bitcoin, buy_pm_ethereum, etc.) without needing the schema opened. It stops short of 5 only because it is a noun phrase with no explicit verb ('Get'/'List') and never names a sibling for comparison.

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 implied rather than stated: 'Live ... odds for solana markets' plus 'Paid ... $0.05 USDC' tells an agent this is a charged, Solana-topic prediction-market lookup. There is no explicit when-to-use/when-not-to-use guidance, no mention of when the free sibling buy_polymarket or the neighbouring topic tools would be a better choice, and no note on repeated calls incurring repeat charges.

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