projectx-mcp

Account snapshot

get_account_snapshot

Read-only

Retrieve an account snapshot: balance, positions, orders, realized P&L vs daily loss limit to guide trading decisions.

Instructions

One-call view of an account: balance, open positions, working orders, and today's realized P&L (trading day starts 17:00 America/Chicago) versus the daily loss limit. Use this to monitor between decisions.

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": {
      "accountId": "<accountId>"
    },
    "name": "get_account_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`accountId`	Yes	Trading account ID from list_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 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 and openWorldHint, so the description does not need to restate safety. It adds valuable context by specifying the included fields and defining the trading day boundary (17:00 America/Chicago), which affects how realized P&L and the loss limit should be interpreted.

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?

Two sentences with no filler: the first packs the full content list plus the timezone qualifier, and the second states the intended use. The most decision-relevant information is front-loaded.

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?

For a single-parameter read-only snapshot, the description adequately covers inputs, output contents, and usage context. The lack of an output schema is mitigated by the explicit enumeration of the snapshot's components.

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 only parameter, accountId, already has a descriptive schema entry ('Trading account ID from list_accounts'), and schema description coverage is 100%. The description adds no extra parameter-level detail, so the baseline 3 applies.

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 opens with 'One-call view of an account' and enumerates the exact contents: balance, open positions, working orders, today's realized P&L, and daily loss limit. This clearly distinguishes it from narrower siblings like list_open_positions or get_performance by emphasizing the composite snapshot nature.

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

Usage Guidelines4/5

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

The closing instruction, 'Use this to monitor between decisions,' gives a clear usage context for a monitoring tool. It does not explicitly name alternatives or state when not to use it, but the intended context is unambiguous enough for an agent.

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