Skip to main content
Glama

SouthPow crypto & market data

buy_pm_trump

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the load and does reasonably well: it discloses the paid model ($0.002 USDC on Base), that no signup or API key is needed, the result ordering (24h volume), and the fields returned. It does not cover payment mechanics, rate limits, or failure behavior, so it is strong but not exhaustive.

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: purpose, returned fields, price, auth, then endpoint URL. The trailing raw URL is the only questionable element, though it may be intentionally informative for direct HTTP use; nothing else is padding.

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?

There is no output schema, but the description enumerates the returned fields (odds per outcome, volume, liquidity, end date, link), which compensates. Cost, auth, and sort order are covered; only pagination/limit behavior is left implicit, which is minor for a one-parameter read tool.

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 a single optional 'limit' parameter whose schema description is fully documented (1-50, default 10), so the schema does the work and a baseline of 3 applies. The description adds nothing about how limit interacts with the volume sort or what happens when fewer markets exist.

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?

States a concrete verb+resource: live Polymarket odds for 'trump' markets, with the sort order and returned fields spelled out. An agent can immediately tell this is the topic-scoped odds endpoint and distinguish it from buy_pm_bitcoin, buy_pm_elon-musk or buy_coin_TRUMP.

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?

It signals this is a 'Paid' endpoint with a stated price and no account/API key required, which helps an agent weigh cost before calling. However, it never says when to prefer this over buy_polymarket (general) or buy_search, and gives no exclusions or fallback guidance.

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