polymarket-trader-mcp

portfolio.optimize

Analyze open positions to generate optimization recommendations based on your risk strategy. Receive stop-loss/take-profit suggestions, concentration warnings, and cut/hold/take-profit actions for each position.

Instructions

Analyze your open positions and generate optimization recommendations based on your chosen strategy (conservative, balanced, or aggressive). Returns SL/TP suggestions, concentration warnings, and cut/hold/take-profit actions for each position.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "portfolio.optimize"
  }
}

Input Schema

Name	Required	Description	Default
`strategy`	No	Risk strategy: conservative=tight SL/TP, balanced=moderate risk, aggressive=wider thresholds for max growth	balanced

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description must carry behavioral disclosure. States it 'analyzes and generates recommendations' with no side effects mentioned. Does not detail the output structure or prerequisites. Some transparency via listed returns, but overall limited.

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?

Single sentence with clear structure: action, method, outcome. No wasted words. Front-loaded with key information.

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?

One-parameter tool with no output schema. Description covers input and output enough for basic usage. Could mention requirement for open positions or how multiple positions are handled, but overall sufficient.

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% with parameter descriptions. The tool description adds context by tying strategy to recommendation generation, but adds minimal extra meaning beyond the schema. Baseline 3 maintained.

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 the tool analyzes open positions and generates optimization recommendations. Specifies what it returns (SL/TP suggestions, concentration warnings, cut/hold/take-profit actions), distinguishing it from siblings like portfolio.risk or positions.list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use when positions exist and optimization is needed, but lacks explicit guidance on when to use this tool vs alternatives (e.g., portfolio.risk or positions.set_exit_rules). No mention of prerequisites or when not to use.

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