Skip to main content
Glama

SouthPow crypto & market data

buy_pm_spacex

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a reasonable job: it discloses cost ($0.002 USDC on Base), that no account or API key is needed, the endpoint URL, the sort order, and the shape of the returned data. It stops short of explaining how payment is transacted (automatic vs. requiring a wallet signature), what happens on failed payment, or 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, front-loaded with 'Paid' and the core purpose, then output fields, then payment/commercial terms, then the URL. Every sentence carries distinct information with no 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?

There is no output schema, and the description compensates by enumerating the returned fields (odds per outcome, volume, liquidity, end date, link). For a one-parameter paid read tool this is close to sufficient; the remaining gap is the mechanics of the payment flow, which matters for a tool that spends money on each call.

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 coverage is 100% and the single parameter already documents its range 1-50 and default of 10, so the heavy lifting is done structurally. The description adds nothing about the limit parameter itself (e.g., that larger values cost more or that 50 is the cap for a single paid call), so the baseline 3 applies.

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 verb and resource ('Live Polymarket odds for spacex markets') plus the sort order (24h volume) and the returned fields, so an agent knows exactly what it fetches. It is inherently differentiated from its buy_pm_* siblings by the 'spacex' topic, but it never explicitly contrasts itself with buy_polymarket or the other topic variants.

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?

The word 'Paid' and the price line signal that this is a paid call, which is useful routing context, and the topic name implies when it is relevant. However, there is no explicit statement of when to choose this over buy_polymarket (all-markets odds) or another buy_pm_* topic tool, and no guidance on whether the cost should make an agent prefer a free alternative first.

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