Skip to main content
Glama

paper_init

Initialize paper trading by setting virtual Bitcoin (BTC) and Indonesian Rupiah (IDR) balances, using defaults or custom amounts.

Instructions

Initialize paper trading with default or custom virtual balances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
btcNoInitial BTC balance (default: 1.0)
idrNoInitial IDR balance (default: 100000000)
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states the tool initializes paper trading but does not indicate whether it is destructive, idempotent, or what happens if paper trading is already initialized. This lack of transparency could lead to incorrect usage.

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?

The description is a single sentence that is clear and front-loaded. It efficiently conveys the core purpose without extraneous words. However, it may be overly concise given the lack of other context.

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

Completeness2/5

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

For a tool with no output schema and no annotations, the description is insufficiently complete. It omits information about return values, side effects, and what constitutes a successful initialization. Given the tool's 2 optional parameters, more context is needed for safe usage.

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?

The input schema has 100% coverage with descriptions for each parameter. The description adds context by mentioning 'default or custom virtual balances', which aligns with the schema. However, it does not add further semantic detail beyond what the schema provides, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as initializing paper trading with balances. The verb 'Initialize' and resource 'paper trading' are specific. It distinguishes from sibling paper_* tools like paper_buy or paper_sell, but does not explicitly differentiate from paper_reset, which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives like paper_reset. There is no mention of prerequisites, scenarios where this tool is appropriate, or when to avoid it.

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/ibidathoillah/indodax-cli'

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