Skip to main content
Glama
Sign In

PropPassCheck

by com.proppasscheck
OverviewDiscussionsAdmin

Find the trade size with the best odds

find_best_size
Read-only

Runs the same trades (or headline numbers) at eight trade sizes, from a quarter to three times, against up to three accounts, and shows the pass and first-payout chance at each with the best size marked. Answers "should I risk less or more per trade on this challenge?". Give trades with starting_balance, or the four headline numbers.

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": {
      "challenge_ids": "<challenge_ids>"
    },
    "name": "find_best_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradesNoClosed trades in the order they closed.
win_rateNoPercentage of trades that win, for example 45.
challenge_idsYesOne to three challenge ids.
reward_to_riskNoAverage win divided by average loss, for example 2 for a 1:2 strategy.
risk_per_tradeNoPercentage of the account lost on a losing trade, for example 1.
trades_per_dayNoAverage trades per trading day, for example 1.5.
starting_balanceNoNeeded with trades.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description builds on that by describing the simulation grid (eight sizes, quarter to three times, up to three accounts) and what the result contains. It omits runtime/compute cost for a 5000-trade simulation, which is the main remaining unknown.

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?

Three front-loaded sentences: what it does, what question it answers, then the two input forms. Nothing is redundant with the schema and no sentence could be dropped without losing routing 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?

For a 7-parameter read-only analysis tool with no output schema, the description covers purpose, input modes and output shape adequately. It does not state whether trades and headline numbers can be mixed, or any minimum data requirements for a meaningful result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description goes further by revealing the mutually exclusive input modes (closed trades with starting_balance vs. the four headline numbers win_rate, reward_to_risk, risk_per_trade, trades_per_day), which the schema itself does not express. The 'four headline numbers' phrasing is mildly indirect but resolvable from 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 operation (re-running the same trades across eight sizes from 0.25x to 3x against up to three accounts) and names the exact outputs (pass chance and first-payout chance with the best size marked). An agent can distinguish this from test_trades or test_stats purely from the description.

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?

Gives the decision the tool answers ("should I risk less or more per trade on this challenge?") and spells out the two input modes: trades plus starting_balance, or the four headline numbers. It stops short of explicitly naming when a sibling tool is the better choice, so a 4 rather than a 5.

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

All PropPassCheck toolsInspect
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