Skip to main content
Glama

SouthPow crypto & market data

buy_pm_interest-rates

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

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_interest-rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the call is paid ($0.05 USDC on Base), that no account or API key is needed, and the endpoint. It stops short of payment flow details (how the charge is incurred, whether it is per-call, failure/refund behavior).

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?

Front-loaded with the paid/live-odds framing, then returned fields, then cost/auth/URL. Dense and free of filler; every clause adds a fact an agent needs before calling.

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-parameter tool with no output schema and no annotations, the description supplies the missing pieces: return fields, cost, auth requirements, and endpoint. Payment mechanics are the only notable omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds meaning by stating results are sorted by 24h volume, which tells the agent that 'limit' selects the top-N by volume rather than an arbitrary slice. It doesn't restate the 1-50 range, but the schema covers that.

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?

Names a specific paid data product (live Polymarket odds), the exact topic scope ('interest rates' markets), the ordering rule (24h volume), and the returned fields. An agent can distinguish this from buy_pm_fed or buy_pm_inflation by the stated market category alone.

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 name and topic. It never states when to choose this over buy_pm_fed, buy_pm_inflation, or the generic buy_polymarket, nor does it say when interest-rate odds are the wrong dataset for a query.

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