polymarket-trader-mcp

config.go_live

Switch from simulated preview to live trading on Polymarket. Confirm to place real orders with real money. Requires API credentials.

Instructions

Switch from preview (simulated) to live trading mode where real orders are placed on Polymarket. Requires API credentials configured in environment. This action uses real money. Pro feature.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "confirm": "<confirm>"
    },
    "name": "config.go_live"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Must be true to confirm switching to live trading mode. This will place real orders with real money

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Disclosure of real money usage is critical behavioral info. Yet no annotations, and missing details like irreversibility or rollback options.

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?

Three short sentences cover purpose, prerequisites, and risk. No redundancy or wasted words.

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?

Adequate for a simple one-param tool without output schema. Could mention that switching is one-way or requires re-authentication later.

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?

Only one parameter with full schema description. The tool description adds no new info beyond the schema's own description of confirm.

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?

Clearly states 'Switch from preview (simulated) to live trading mode' with specific verb and resource. Distinct from sibling config tools like config.dashboard or config.set.

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?

Mentions prerequisites (API credentials, pro feature) and the real-money risk, but does not explicitly state when not to use (e.g., test in preview first).

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