Skip to main content
Glama

SouthPow crypto & market data

buy_pm_elon-musk

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

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_elon-musk"
  }
}

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, the description carries the burden and does well: it discloses the cost ($0.10 USDC on Base), the payment rail, that no auth is required, and the default sort order (24h volume). It stops short of saying whether payment is per-call or per-result, or what happens on payment failure, which keeps it out of the top band.

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?

A single dense sentence front-loads the paid status and the core value proposition, followed by a terse cost/auth line and the endpoint URL. Every clause carries information, though the trailing raw URL is slightly clunky and the return-field list is compressed into one run-on.

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 covers what the call returns, what it costs, what auth it needs, and how results are ordered. Only error behavior and payment-failure semantics are missing, which are minor for a read-only odds lookup.

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?

There is a single optional parameter (limit) and schema coverage is 100%, with the schema itself documenting the 1-50 range and default of 10. The description adds no semantics beyond that, so the baseline of 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 resource (live Polymarket odds for 'elon musk' markets) and enumerates the returned fields: odds per outcome, volume, liquidity, end date, link. The topic scope plus the buy_pm_<topic> sibling naming convention makes it distinguishable from buy_pm_trump or buy_polymarket without opening the schema, though it never explicitly states the alternative.

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?

Useful context is implied rather than stated: 'Paid' plus the price signals this is a cost-bearing call, and 'No account, no API key' tells the agent no setup is needed. However, there is no explicit when-to-use/when-not guidance, no mention of the free generic buy_polymarket sibling, and no statement about when the paid call is worth it over alternatives.

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