polymarket-paper-trader

List limit orders

list_orders

Read-onlyIdempotent

Retrieve pending limit orders for a Polymarket paper-trading account from local storage without modifying data. Use it to review open orders before checking fills or canceling.

Instructions

List an account's pending limit orders.

Reads the local database only and changes nothing. Use check_orders to evaluate them against live prices, or cancel_order to remove one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account`	No	Paper account name; any name without '/', '\', '..' or surrounding spaces. Each name is a separate local account. Default 'default'.	default

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.13Oct 16, 2026

addedInput schema / properties / account / description

Added value: +"Paper account name; any name without '/', '\\', '..' or surrounding spaces. Each name is a separate local account. Default 'default'."

First observedv0.4.1Sep 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true), so the bar is lower. The description still adds real value by disclosing that it reads the local database only and does not touch live market state, a distinction annotations do not convey.

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, zero filler, with the core purpose front-loaded and the alternatives trailing. Every sentence earns its place.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. The description supplies the local-only read semantics and the sibling routing, leaving nothing an agent needs to call it correctly.

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%, so the schema fully documents the single 'account' parameter and its naming rules. The description adds nothing about parameters, which is the expected baseline when the schema does the heavy lifting.

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: 'List an account's pending limit orders.' It scopes the operation to local pending limit orders and names the two siblings an agent might confuse it with (check_orders, cancel_order), so it is distinguishable without opening a 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?

Explicitly routes to alternatives: check_orders for live-price evaluation and cancel_order for removal, giving the condition that selects each. It stops short of stating when to reach for list_orders itself beyond the implied 'you want to see pending orders', so it is strong but not exhaustive.

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