Skip to main content
Glama

SouthPow crypto & market data

buy_pm_tennis

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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.25 USDC on Base), that no account or API key is needed, and exactly what fields come back. It does not explain how the charge is executed (prepay, x402 challenge, or per-call deduction) or what happens if payment fails.

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?

Terse, front-loaded fragments: payment status first, then what you get, then price and access model, then endpoint. No sentence is padding for a one-parameter tool.

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 single optional parameter with no output schema, the description covers the returned fields, cost, and access model well. The one meaningful gap is the payment mechanism and failure behavior for a paid endpoint, which an agent would want before committing $0.25.

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% with a single parameter whose range and default are already documented. The description's sort-order detail is about results, not the limit parameter, so it adds no meaning beyond the schema — baseline 3 applies.

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?

States a specific verb and resource (live Polymarket odds) scoped to 'tennis' markets, plus the sort order (24h volume). An agent can distinguish it from buy_pm_soccer, buy_pm_nba, or the generic buy_polymarket purely from the description.

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 topic name — an agent infers 'use this for tennis prediction-market odds.' There is no explicit when-not guidance and no pointer to the generic buy_polymarket sibling for other topics or broader 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