Skip to main content
Glama
monsterbyurbed11

Alpha402

by monsterbyurbed11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Polymarket High-Volume Prediction Markets & Arbitrage Spreads

get_polymarket_alpha
Read-onlyIdempotent

Retrieves high-volume active Polymarket prediction markets with outcome probabilities, USD liquidity depth, and binary arbitrage spreads; includes three free daily calls, then $0.01 USDC per call.

Instructions

Retrieves the highest-volume active prediction markets on Polymarket along with outcome probabilities, liquidity depth in USD, and binary arbitrage spreads. Includes 3 free calls/day; unlimited calls cost $0.01 USDC.

Input Schema

NameRequiredDescriptionDefault
paymentProofNoOptional Base USDC transaction hash ("0x...") or HTTP 402 payment proof for unlimited calls after your 3 free daily queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.6.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / paymentProof
      Added value: +{
+  "description": "Optional Base USDC transaction hash (\"0x...\") or HTTP 402 payment proof for unlimited calls after your 3 free daily queries.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds important operational context beyond annotations: the free-call allowance and the paid USDC requirement for unlimited calls.

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?

Two sentences with no wasted wording. The core data-retrieval purpose is front-loaded, followed by the payment constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only retrieval tool with one optional parameter and no output schema, the description provides enough context: it explains what data is returned and the payment/free-tier model.

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 description coverage is 100%, and the sole optional paymentProof parameter is fully documented in the schema. The description reinforces the payment concept but does not add parameter-level meaning beyond what the schema already provides, matching the baseline for high coverage.

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?

The description states a specific verb and resource: retrieving highest-volume active prediction markets on Polymarket. It also names the returned content, distinguishing it clearly from sibling tools focused on token security, credits, new pairs, or token alpha.

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 tool's domain is clear from the description, so usage is strongly implied for Polymarket prediction-market data. However, it does not explicitly state when to use this versus sibling tools or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools