Skip to main content
Glama

SouthPow crypto & market data

buy_pm_weather

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

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

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 supplies valuable operational context: it is paid, costs $0.25 USDC on Base, requires no account or API key, provides live data, and sorts results by 24-hour volume. It also lists returned fields and the endpoint, though it does not explicitly state whether the fee is per call or confirm that no market position is purchased.

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?

The description is compact and front-loaded, with each fragment adding scope, cost, authentication, output, or endpoint information. There is no substantive filler.

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 simple one-parameter feed, it covers nearly everything needed to select and invoke it: topic, freshness, ordering, result fields, price, network, authentication requirements, and URL. The field list mitigates the lack of an output schema, but explicit per-call billing and read-only/no-betting behavior would remove the remaining ambiguity.

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?

The sole optional limit parameter is fully documented in the schema, including its 1–50 range and default of 10, so the baseline is 3. The description adds no limit-specific syntax or constraints, although its sorting details help clarify what the limited result set contains.

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 identifies a live Polymarket odds feed specifically for weather markets and states its 24-hour-volume ordering. This scope clearly distinguishes it from the other buy_pm_* topic tools and the broader buy_polymarket sibling.

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

Usage Guidelines4/5

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

It provides a clear use case: retrieving current odds for weather-related Polymarket markets. However, it does not explicitly explain when to choose this over buy_polymarket or clarify that the tool retrieves data rather than placing a wager.

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