Skip to main content
Glama

SouthPow crypto & market data

buy_pm_ethereum

Paid. Live Polymarket odds for 'ethereum' markets, sorted by 24h volume: odds per outcome, volume, liquidity, end date, link. $0.01 USDC on Base. No account, no API key. URL https://southpow.media/v1/polymarket/ethereum.

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

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 carries the full burden and does most of it: it discloses the cost, payment chain, no-auth requirement, default sorting, and the returned fields (odds per outcome, volume, liquidity, end date, link). Missing are failure modes, rate limits, and whether cost is per-call or per-result, which keeps it from a 5.

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?

Front-loaded with 'Paid.' before anything else, then topic, sort order, returned fields, cost, auth, and endpoint. Telegraphic fragments with no filler; every sentence carries a distinct fact.

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 tool with no output schema and no annotations, the description supplies the return shape, ordering, price, and payment requirements, which is close to sufficient. It leaves open pagination behavior and what a truncated or empty market list looks like.

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 only parameter (limit, 1-50, default 10) is fully documented in the schema, so per the baseline rule this is a 3. The description adds no meaning about limit beyond noting the result is volume-sorted, which is not a parameter constraint.

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 for ethereum markets') plus the ordering ('sorted by 24h volume'), which clearly distinguishes it from the other buy_pm_* topic tools and from buy_polymarket. An agent can identify the topic scope without opening the schema.

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?

'Paid. ... $0.01 USDC on Base. No account, no API key.' gives the agent the key precondition for deciding whether to call at all, and the topic-specific title implies when it is the right sibling. It does not explicitly name an alternative (e.g. buy_polymarket for all markets) or state when not to use it, so it falls short of a 5.

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