Skip to main content
Glama
agent-next

polymarket-paper-trader

by agent-next

reset_account

Reset your paper trading account by clearing all trades, positions, and balance to start a new simulation.

Instructions

Reset account — deletes all trades, positions, and balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNodefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states the destructive effect: deletes all trades, positions, and balance. It does not mention reversibility, permissions, or post-reset account state, but the core destructive behavior is clearly conveyed.

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?

A single sentence that is front-loaded with the action and resource, followed immediately by the most important behavioral consequence. There is no filler or redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one optional parameter and an output schema, and the description covers the essential destructive effect. However, it omits usage context and what happens to the account after reset, leaving a moderate gap for a destructive operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate for the undocumented 'account' parameter. It does not add any meaning beyond the parameter name and default value, though the tool name weakly implies the account parameter identifies which account to reset.

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?

The description uses a specific verb and resource ('Reset account') and explicitly enumerates what gets deleted: all trades, positions, and balance. This clearly distinguishes it from siblings like init_account, buy, and sell.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives such as init_account, nor are any prerequisites or exclusions mentioned. The usage context is only implied by the word 'Reset'.

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