polymarket-paper-trader

Generate share content

share_content

Read-onlyIdempotent

Generate post-ready stats text for Twitter, Telegram, Discord, or plain output from a paper trading account, using performance, milestone, or daily templates.

Instructions

Generate post-ready text for a platform and template from one account's stats.

Reads the local account and posts nothing. Open positions are valued at live midpoints (0 if a lookup fails). Use this when you need a template (milestone, daily); use stats_card for a plain stats card or stats for raw numbers.

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
`platform`	No	'twitter', 'telegram', 'discord' or 'plain'. Default 'twitter'.	twitter
`template`	No	'performance' (stats overview), 'milestone' (achievement) or 'daily' (daily report with positions). Default 'performance'.	performance

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields 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'."

addedInput schema / properties / platform / description

Added value: +"'twitter', 'telegram', 'discord' or 'plain'. Default 'twitter'."

addedInput schema / properties / template / description

Added value: +"'performance' (stats overview), 'milestone' (achievement) or 'daily' (daily report with positions). Default 'performance'."

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 declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds real context beyond them: 'Reads the local account and posts nothing' and the valuation rule 'Open positions are valued at live midpoints (0 if a lookup fails).' That failure-fallback behavior is not derivable from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then side-effect and valuation facts, then routing. The sentence fragments ('use stats_card for...') are terse and earn their place, though the line breaks make the structure slightly ragged.

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?

An output schema exists, so return formatting needn't be explained. Purpose, side-effect profile, valuation behavior and sibling routing are all covered; the only small gap is not naming the default 'performance' template in the prose.

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 the schema already documents account, platform and template with defaults and allowed values. The description adds only partial semantics (milestone/daily templates) and omits the default 'performance' template, so it doesn't meaningfully exceed the baseline.

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?

Specific verb+resource: 'Generate post-ready text for a platform and template from one account's stats.' It explicitly distinguishes itself from the sibling tools stats_card and stats, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Names the alternatives and the condition that selects each: 'use stats_card for a plain stats card or stats for raw numbers,' and scopes this tool to templated output (milestone, daily). Routing is unambiguous.

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