FILTRIX.net

create_paper_account

Open the caller's paper account (one per user) with simulated capital and risk limits. Paper money only: nothing places a real order. Check get_paper_status first (has_account). If the account already exists, change its limits with update_paper_limits or start over with reset_paper_account. Next: get_paper_catalog to build a strategy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limits": "<limits>"
    },
    "name": "create_paper_account"
  }
}

Input Schema

Name	Required	Description	Default
`limits`	Yes	Risk limits: max_open_risk (USD, decimal string: total risk to the stops of all open positions), daily_loss_limit (USD, decimal string: an equity drop since the session start that stops new entries for the session), max_symbols (integer 1..1000: symbols held at once). Example: {"max_open_risk": "2000", "daily_loss_limit": "1000", "max_symbols": 5}.
`capital`	No	Simulated capital in USD as a decimal string, e.g. '100000'.	100000
`idempotency_key`	No	Optional key that makes a retry safe: the same key replays the first answer instead of acting twice. Derived from the other arguments when omitted.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds context the annotations cannot convey: that the state is simulated ('Paper money only: nothing places a real order') and that ownership is one-per-user. This is valuable given openWorldHint=true, which alone might suggest real-world side effects. It does not discuss how the idempotency_key interacts with the declared idempotentHint=false, which is a minor gap for a creation tool.

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?

Four short sentences, front-loaded with the core action and constraint, then preconditions, then the next step. Every sentence routes or constrains the agent; nothing is filler.

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

Completeness5/5

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

Output schema exists so return values need not be explained, and the schema fully documents parameters. What remains — the precheck, the alternatives for an existing account, and the follow-up step — is all present, so an agent has everything needed to invoke it correctly.

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%, with limits, capital and idempotency_key all documented in detail in the schema, so the baseline is 3. The description only alludes vaguely to 'simulated capital and risk limits' and adds no new meaning beyond the schema.

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?

States a specific verb and resource ('Open the caller's paper account') plus the key scope constraints: one account per user, simulated capital and risk limits. It also explicitly names the sibling tools (get_paper_status, update_paper_limits, reset_paper_account) so the agent can distinguish this from adjacent operations.

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?

Gives explicit when-to-use and when-not-to-use guidance: check get_paper_status (has_account) first, use update_paper_limits if the account exists, use reset_paper_account to start over, and go to get_paper_catalog next. Alternatives and their triggering conditions are all spelled out.

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

All FILTRIX.net tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?