projectx-mcp

Performance statistics

get_performance

Read-only

Evaluate trading performance with win rate, net P&L, average win/loss, profit factor, expectancy, overall and per contract for a specified time window. Grade your trading results.

Instructions

Win rate, net P&L after fees, average win/loss, profit factor, expectancy, overall and per contract, for a time window (default: current trading day). Use it to grade your own trading.

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_performance"
  }
}

Input Schema

Name	Required	Description
`accountId`	Yes	Trading account ID from list_accounts.
`endTimestamp`	No
`startTimestamp`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, reducing the burden on the description. The description adds useful behavioral context: metrics are net of fees, and the time window defaults to the current trading day. No contradictions with annotations.

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 a single, tight sentence that front-loads the key metrics and ends with a clear usage cue. No filler, no repetition of schema details, and every phrase contributes value.

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

Completeness4/5

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

With no output schema, the description compensates by listing the returned performance metrics. It also notes the default time window and fee adjustment. Minor gaps remain around timestamp interpretation and per-contract grouping semantics, but for a read-only statistics tool this is reasonably complete.

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?

Only accountId has a schema description (33% coverage), so the description must compensate for the undocumented startTimestamp and endTimestamp. It does add meaning by explaining the 'time window' concept and the default (current trading day), but it omits details like timezone handling or inclusivity. Partial compensation.

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 enumerates specific performance metrics—win rate, net P&L after fees, average win/loss, profit factor, expectancy—and clarifies scope as 'overall and per contract' over a time window. This clearly identifies the resource and distinguishes it from siblings like get_quote or get_bars, even without an explicit verb.

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?

'Use it to grade your own trading' provides clear contextual intent for when the tool is appropriate. It does not explicitly name alternatives or exclusions, but the performance-statistics framing is distinct enough among the sibling tools to guide selection.

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