Skip to main content
Glama
agent-next

polymarket-paper-trader

by agent-next

init_account

Set up a paper trading account with a specified starting balance, creating a new account or resetting an existing one to begin trading strategies.

Instructions

Initialize a paper trading account with starting balance (USD).

Creates a new account or resets an existing one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNodefault
balanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool creates or resets an account, but it does not disclose what a reset destroys, such as existing balance or history, whether the operation is reversible, or any permission implications. For a state-changing tool, this is a meaningful gap.

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?

The description is two short sentences with no filler. The core purpose is front-loaded, and the additional create/reset behavior is stated clearly in the second sentence.

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?

For a simple two-parameter tool with an output schema available, the description is nearly adequate. However, it omits the destructive implications of resetting and gives no guidance on the account parameter, so an agent may not fully understand the consequences before invoking the tool.

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?

The schema provides no parameter descriptions (0% coverage), so the description must compensate. It adds that the balance is a USD starting balance, which is useful, but it leaves the account parameter completely unexplained beyond its default value. The compensation is only partial.

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 states a specific verb and resource: initialize a paper trading account with a USD starting balance. It further clarifies that it creates a new account or resets an existing one, distinguishing it from trading operations like buy/sell and from the sibling reset_account by covering creation as well.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tools are named. The phrase 'Creates a new account or resets an existing one' implies it is the setup/reset entry point, but it does not explain how this relates to the sibling reset_account tool.

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