Skip to main content
Glama

SouthPow crypto & market data

buy_pm_inflation

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

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

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 provided, the description carries the full burden and does well: it discloses that the call is paid ($0.10 USDC on Base), that no account or API key is required, the sort order applied to results, and the shape of returned data. What it omits is the payment mechanics (how the USDC charge is executed, e.g. x402 handshake), rate limits, and failure behavior on unpaid requests — meaningful gaps for a paid endpoint.

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?

Front-loaded with 'Paid.' so the cost signal arrives before anything else, and the rest is a dense field/terms list with no filler. The telegraphic style ('odds per outcome, volume, liquidity, end date, link') is efficient but reads as fragments rather than prose, and the raw URL at the tail is untagged as the endpoint.

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 compensates well by listing the returned fields and stating cost and auth requirements. The main missing piece is how payment is actually settled for a paid endpoint, which is the one thing an agent could get wrong when invoking it.

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?

Only one parameter (limit) exists and schema description coverage is 100%, so the schema already documents the range and default. The description says nothing about limit at all, adding zero meaning beyond the schema, but the baseline of 3 applies when the schema does the documentation 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 names a specific resource (live Polymarket odds for 'inflation' markets) with a stated sort order (24h volume) and enumerates the returned fields (odds per outcome, volume, liquidity, end date, link). That is enough to distinguish it from buy_pm_interest-rates, buy_pm_fed, and buy_pm_recession by topic alone, though it never explicitly says how it differs from those adjacent macro topics.

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 keyword — an agent must infer that it should call this when the user asks about inflation-linked prediction markets. There is no explicit when-to-use, when-not-to-use, or named alternative such as buy_pm_interest-rates or the generic buy_polymarket. The cost disclosure ('$0.10 USDC on Base') does give useful buy/skip context.

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