Skip to main content
Glama

SouthPow crypto & market data

buy_pm_israel

Paid. Live Polymarket odds for 'israel' 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/israel.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 well: it discloses that the call is paid ($0.05 USDC on Base), that no account or API key is needed, and that results are sorted by 24h volume. It stops short of explaining how the payment is executed or what happens on payment failure, which keeps it from a 5.

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 compact and front-loaded: paid status first, then what is returned, then cost/auth, then endpoint. The telegraphic style ('Paid.', bare URL, no verbs in places) is efficient but slightly reads as a listing rather than prose.

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 simple one-parameter read tool with no output schema, the description covers the returned fields (odds per outcome, volume, liquidity, end date, link), the sort order, and the payment model. The main remaining gap is the mechanics of the paid call, which an agent would need before invoking.

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% with a single optional 'limit' parameter (1-50, default 10), so the schema fully documents the input. The description adds nothing about the parameter, which is the expected baseline when the schema does the work.

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 states a specific resource and scope: live Polymarket odds for 'israel' markets, sorted by 24h volume. That distinguishes it from topical siblings like buy_pm_trump or buy_pm_ukraine and from the generic buy_polymarket, though it doesn't explicitly say how it relates to buy_polymarket.

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 by the topic name and the 'Paid' framing, and it states there is no account or API key required. However, it gives no explicit when-to-use/when-not guidance and never names the alternative tool (e.g. buy_polymarket for broader coverage) an agent should pick instead.

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