Skip to main content
Glama

SouthPow crypto & market data

buy_pm_soccer

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

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

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 full 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 that results are sorted by 24h volume. It stops short of failure modes, rate limits, or error/settlement behavior for the payment.

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?

Front-loaded with 'Paid.', then purpose, output shape, pricing/auth, and endpoint URL. Dense and free of filler, though the raw URL arguably belongs in metadata rather than prose.

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, it covers what is returned, how results are ordered, cost, and auth requirements — everything an agent needs to decide and call. Payment mechanics (how the $0.05 is actually collected) and error handling remain unstated.

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 'limit' parameter (1-50, default 10) is fully documented in the schema. The description does not mention it at all, so it adds nothing beyond structured data — 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?

States a specific resource ('live Polymarket odds for soccer markets') with the sort order (24h volume) and the fields returned. The domain word 'soccer' inherently separates it from the many buy_pm_* siblings, though it never explicitly contrasts with them or with the generic buy_polymarket.

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 context is implied by the domain-specific name and the 'Paid' flag, but there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as buy_polymarket or buy_search for broader market queries.

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