Skip to main content
Glama
demwick

Polymarket Agent Mcp

config.log_cycle

Record AI agent trading cycle metrics including PnL, win rate, and positions to database after each automated cycle for dashboard tracking and performance analysis.

Instructions

Record an AI agent's trading cycle metrics to the database for dashboard tracking and performance analysis. Stores PnL, win rate, positions, budget usage, and notes. Call this after each automated trading cycle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_nameYesName of the AI agent logging this cycle
strategyYesTrading strategy used in this cycle (e.g. 'copy_top_traders', 'stink_bids')
statusNoCycle outcome: ok=normal, warning=minor issue, risk_alert=needs attention, error=failedok
positions_openNoNumber of currently open positions
positions_closedNoNumber of positions closed this cycle
realized_pnlNoRealized profit/loss in USDC from closed positions
unrealized_pnlNoUnrealized profit/loss in USDC from open positions
win_rateNoWin rate as a decimal (0.0-1.0)
budget_usedNoAmount of daily budget spent in USDC
budget_limitNoTotal daily budget limit in USDC
actions_takenNoComma-separated list of actions taken (e.g. 'bought YES on Bitcoin market')
notesNoFree-text notes about this cycle
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions recording to database (write operation) but lacks details on side effects, auth needs, or idempotency. Acceptable but not thorough.

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, front-loaded with purpose and key fields. No fluff, every sentence is informative.

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?

Description covers purpose, timing, and stored fields. No output schema needed. Sufficient for an agent to understand usage. Could mention return value or effect, but not critical.

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%, so baseline is 3. Description adds a brief summary (PnL, win rate, etc.) but does not add meaningful semantics beyond the schema.

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?

Description states specific verb 'Record' and resource 'AI agent's trading cycle metrics to the database'. It clearly distinguishes from sibling tools, none of which are for logging cycle metrics.

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 states when to call ('after each automated trading cycle'). No explicit when-not or alternatives, but the specificity suffices for this logging tool.

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-agent-mcp'

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