Skip to main content
Glama

SouthPow crypto & market data

buy_pm_election

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does substantial work: it discloses that the call is paid ($0.25 USDC on Base), requires no account or API key, sorts by 24h volume, and lists the return fields. It leaves open how payment is actually settled (e.g., x402 flow), behavior on payment failure, and whether results are paginated beyond the limit parameter.

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?

A single dense sentence front-loads the most decision-critical fact ('Paid'), then scope, payload, cost, and endpoint with no filler; every clause carries distinct information.

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-parameter, no-output-schema tool, the description effectively serves as the output schema by enumerating returned fields, and it covers cost and auth prerequisites. The remaining gap is operational: the mechanics of paying $0.25 USDC and what happens when payment is missing or the limit is out of range.

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?

There is only one parameter and the schema documents it fully at 100% coverage ('Markets, 1-50 (default 10)'), so the baseline of 3 applies. The description adds only the sorting semantics (24h volume), which is not a parameter but does help interpret the limit ordering.

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?

The description states a specific resource (Polymarket 'election' markets) and enumerates the exact payload returned (odds per outcome, volume, liquidity, end date, link), which is enough to distinguish it from the many topical siblings such as buy_pm_trump or buy_pm_fed.

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 by the topic name: an agent can infer that this tool covers election markets and that other buy_pm_* tools cover other topics, but the description never states when to choose this over buy_polymarket or a sibling, nor any exclusions such as market-type or date-range coverage.

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