Canonical tool surface
This page reflects the current canonical MCP surface asserted by the server smoke test onmain.
The server is organized around a smaller set of wrapper-style entry points:
list_marketsselects listing shape and retrieval mode withviewandmode- market data is exposed through pluralized batch tools like
get_order_booksandget_prices - auth flows are centered on
ensure_api_key,prepare_order,place_order,cancel_orders,get_rewards, andget_rewards_market_details - transaction building is unified under
build_transactions - relayer execution is unified under
relayer_execute
1) Public market discovery
These tools work without credentials.list_markets
list_markets is the canonical listing entry point. It accepts:
viewto choose payload shapemodeto choose listing modenext_cursorfor pagination
2) Batched market data
Use these tools when you already have one or moretoken_id values and want consistent batch responses.
Example:
items[].side is required for side-aware tools like get_prices. Including side in other batched calls is still useful for a uniform workflow shape.3) Authenticated trading and account wrappers
These tools require configured Polymarket credentials.prepare_order
prepare_order prepares or signs an order locally without posting it.
kind: "limit"expectspriceandsizekind: "market"expectsamount
place_order
place_order is the canonical order-posting wrapper. It uses source to select the posting path:
source: "draft"for create-and-post from a draft ordersource: "signed"for posting one pre-signed ordersource: "signed_batch"for posting a batch of pre-signed orders
confirm: true is required.
cancel_orders
cancel_orders is the canonical cancellation wrapper. It uses:
mode: "ids"mode: "all"mode: "market"
confirm: true is required.
get_rewards
get_rewards uses a scope selector:
daytotal_daycurrentpercentagesuser_market_config
get_rewards_market_details when you need market-specific reward details for a condition_id.
4) Bridge and transaction building
Bridge tools
bridge_supported_assetsbridge_create_deposit_addressesbridge_get_transaction_status
build_transactions
build_transactions is the canonical transaction-builder wrapper. Pass an items array where each item declares a kind plus its required fields.
Representative kind values include:
erc20_approval,erc1155_approval,erc20_transfer,eth_transferwithdraw_on_maticsplit_positions,merge_positions,redeem_positionsbuy_market_outcome,sell_market_outcomeadd_funding,remove_fundingneg_risk_convert_positions,neg_risk_redeem_positionsproxy_wallet_address,index_set,market_index
5) Relayer and builder-relayer
Use these when transaction lifecycle tracking matters.Relayer tools
relayer_get_relay_addressrelayer_get_noncerelayer_get_relay_payloadrelayer_get_transactionsrelayer_executerelayer_deploy_saferelayer_poll_until_state
relayer_execute is the canonical relayer execution wrapper. It accepts:
execution_type: "proxy" | "safe" | "manual"transactions- optional
metadata - optional
gas_limit/gas_pricefor manual mode confirm: true
Builder-relayer tools
builder_relayer_get_noncebuilder_relayer_get_relay_payloadbuilder_relayer_get_transactionsbuilder_relayer_executebuilder_relayer_deploybuilder_relayer_get_deployedbuilder_relayer_poll_until_state

