Skip to main content
Glama
demwick

polymarket-trader-mcp

wta.discover

Identify discounted favorites in today's WTA tennis matches on Polymarket. Compares current price to fair price, returns matches with discount percentage for stink bid opportunities.

Instructions

Find today's WTA tennis match markets on Polymarket where the favorite is available at a discount. Returns matches with current price vs fair price and the discount percentage. Use place_stink_bid to act on these opportunities. Pro feature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
discount_pctNoMinimum discount percentage below fair price to qualify as a stink bid opportunity (5-50%)
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It notes it's a 'Pro feature' but lacks details on side effects, rate limits, or authentication needs. The tool likely is read-only, but this is not stated.

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?

The description is three sentences, front-loaded with the core purpose, then the return value, then the action to take. No wasted words; every sentence earns its place.

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 discovery tool, the description adequately explains what it returns (current price, fair price, discount percentage). No output schema exists, but the description fills the gap well. Still, lacks details on result limits or pagination.

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?

The single parameter (discount_pct) has high schema coverage with description in the schema itself. The description repeats the schema's meaning without adding new semantic context, so it meets but does not exceed the baseline.

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 clearly states it finds WTA tennis match markets on Polymarket where the favorite is discounted, returning price comparisons and discount percentage. This is specific and distinguishes it from siblings like wta.bid or markets.discover.

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?

The description explicitly advises to use place_stink_bid for acting on opportunities, providing clear next-step guidance. However, it does not mention when not to use or compare to alternative tools like traders.discover.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/demwick/polymarket-trader-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server