Skip to main content
Glama

SouthPow crypto & market data

buy_pm_recession

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 reasonably well: it discloses the cost ($0.25 USDC on Base), that no account or API key is required, the sort order, and the fields returned. It omits important payment behavior such as whether repeat calls are charged again, what happens on payment failure, and any 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?

Compact and front-loaded: price and payment rail come first, then the payload description, then access requirements. The literal endpoint URL is slightly redundant if the tool config already carries it, but every other clause carries 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-optional-param tool with no output schema, the description enumerates the returned fields (odds per outcome, volume, liquidity, end date, link), which substitutes for a missing output schema. The gap is payment-lifecycle behavior for a paid endpoint, which an agent about to spend USDC would benefit from knowing.

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%, so the single optional 'limit' parameter (1-50, default 10) is already fully documented in the schema. The description adds nothing about it, though it does explain the ordering of results, which is related but not a parameter. Baseline 3 applies when the schema does the heavy lifting.

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 resource and scope: live Polymarket odds for 'recession' markets, sorted by 24h volume, with the exact fields returned. That topic specificity separates it from siblings such as buy_pm_inflation or buy_pm_fed without needing the name. It never explicitly frames the action as a paid purchase beyond the leading word 'Paid', so it stops just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says when recession-market odds are the right data versus a related topic tool like buy_pm_inflation or buy_pm_fed, and no exclusions are stated. The only routing signal is the topic word embedded in the description, which the agent must infer.

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