Skip to main content
Glama

SouthPow crypto & market data

buy_pm_ukraine

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

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

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?

No annotations exist, so the description carries the full burden, and it does disclose the essentials: the call is paid at a fixed $0.01 USDC price, requires no credentials, and returns results ordered by 24h volume. It omits failure behavior (empty result sets, payment failure) and 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.

Conciseness4/5

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

Dense and front-loaded: price first, then content, then payment mechanics and endpoint. Slightly telegraphic (colon-separated field list), but no sentence is wasted.

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?

A single-parameter read tool with no output schema, so the description's enumeration of return fields (odds per outcome, volume, liquidity, end date, link) plus sort order and cost covers what an agent needs. Only edge-case behavior is missing.

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 coverage is 100% and the single 'limit' parameter is documented there (1-50, default 10). The description adds nothing about the limit parameter, so 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?

States a specific verb and resource: live Polymarket odds restricted to 'ukraine' markets, sorted by 24h volume. The topic scoping is explicit and separates it from the many buy_pm_* topic siblings, though it never names buy_polymarket (the general variant) as the broader alternative.

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?

Gives practical access context ('Paid', '$0.01 USDC on Base', 'No account, no API key'), which tells the agent it can call this without setup. It does not say when to choose this over buy_polymarket or a different buy_pm_* topic, nor 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