canli-validation-mcp

Check a plan against broker limits and impact

check_feasibility

Read-onlyIdempotent

Validates a trading plan against broker order-rate and minimum-order limits, day-trading rules, market-impact costs, and capital thresholds where costs erase returns.

Instructions

Check a trading plan before it trades: broker order-rate and minimum-order limits, 2026 US day-trading rules, square-root market impact with crowding, and the capital where costs eat the return. Checks the plan as described against published broker limits and a market-impact model; it never contacts a broker or sees an account.

Input Schema

TableJSON Schema

Name	Required	Description
`broker`	No	Default other.
`copies`	No	Agents trading the same signal at once; default 1.
`account`	No
`adv_usd`	Yes	Daily dollar volume of a typical holding.
`asset_class`	No
`capital_usd`	Yes
`daily_volatility`	Yes	Of a typical holding, e.g. 0.02.
`turnover_per_year`	Yes	Buys plus sells a year / capital.
`impact_coefficient`	No	Square-root law Y; default 1.
`rebalances_per_year`	Yes
`spread_and_fees_bps`	No	Per trade; default 0.
`orders_per_rebalance`	Yes
`expected_gross_return`	No	Annual, before costs; adds capacity.
`minutes_per_rebalance`	No	Default 1.
`orders_per_minute_limit`	No	If the broker's is not on file.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`checks`	No
`limits`	No
`sources`	No
`verdict`	No
`to_change`	No
`plain_reading`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.13.0Oct 7, 2026
- removedInput schema / properties / copies / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / copies / minimum
```
Removed value: --9007199254740991
```
- removedInput schema / properties / orders_per_rebalance / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / orders_per_rebalance / minimum
```
Removed value: --9007199254740991
```
- removedOutput schema / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / sources / additionalProperties
```
Removed value: -{}
```
Addedv0.12.0Oct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/idempotent/destructive, so the bar is lower. The description still adds value: it enumerates the specific rules and models applied (2026 US day-trading rules, square-root impact with crowding) and clarifies the tool performs a pure computation with no broker or account access.

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?

Two sentences, front-loaded with the check and the scope of the model, followed by the isolation constraint. Dense but no filler; the second sentence's boundary statement earns its place.

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?

An output schema exists, so return-value explanation is not needed. For a 15-parameter modeling tool the description conveys the model's components and its read-only, offline nature, though it leaves the roughly one-third of undocumented parameters to the schema alone.

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 coverage is 67%, a middle band where the schema documents most inputs on its own. The description gestures at parameter domains (broker order-rate limits, impact, cost capacity) but gives no syntax, units, or defaults beyond what the schema already states, so it neither compensates for the gap nor repeats the schema.

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?

Specific verb (check) and resource (a trading plan) with a tightly bounded scope — broker limits, day-trading rules, market impact, and cost capacity — that reads distinctly from the validate_* and backtest_strategy siblings. It does not, however, explicitly name any sibling to differentiate itself from them.

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?

'Check a trading plan before it trades' gives a clear usage context (pre-trade feasibility screening) and the closing clause states a boundary (never contacts a broker, never sees an account). No explicit when-not-to-use or routing to an alternative sibling is provided.

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