Algo Trade Analytics

propose_strategy_candidate

propose_strategy_candidate

Read-onlyIdempotent

Produce a free-form Pine candidate tied to a hypothesis and expected mechanism. Prerequisite: the FIRST call in a session is refused until inspect_market_context and analyze_losing_trades have each succeeded, so run both diagnostics before proposing (the loss diagnostic is waived only when the baseline closed no trades).

Input Schema

TableJSON Schema

Name	Required	Description
`rationale`	No
`hypothesis`	Yes
`caseStudyId`	No	Optional: bind this call to one of your case studies. Defaults to the bound run's case study.
`researchRunId`	No	Optional: bind this call to one of your existing research runs. Defaults to this session's most recent unfinished run.
`baselineSource`	No	Pine source the candidate derives from. Omit it, or pass "platform_benchmark", to derive from the platform benchmark baseline for the bound scope (EMA 20/50 long-only crossover declaring 1bp commission per side and 2 ticks slippage). Never write your own baseline: a hand-written one with no declared costs is honoured verbatim by every later comparison and fails cost sensitivity.
`candidateSource`	Yes
`mcpIdempotencyKey`	No	Unique key for this logical action. Reuse it only when retrying the same arguments. Required for hosted trust-creating actions when no idempotency header is supplied.
`changesFromBaseline`	Yes
`similarityThreshold`	No
`priorCandidateSources`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 17, 2026

addedInput schema / properties / baselineSource / anyOf

Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / baselineSource / description

Added value: +"Pine source the candidate derives from. Omit it, or pass \"platform_benchmark\", to derive from the platform benchmark baseline for the bound scope (EMA 20/50 long-only crossover declaring 1bp commission per side and 2 ticks slippage). Never write your own baseline: a hand-written one with no declared costs is honoured verbatim by every later comparison and fails cost sensitivity."

removedInput schema / properties / baselineSource / minLength
```
Removed value: -1
```
removedInput schema / properties / baselineSource / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "baselineSource",
-  "candidateSource",
-  "hypothesis",
-  "changesFromBaseline"
-]New value: +[
+  "candidateSource",
+  "hypothesis",
+  "changesFromBaseline"
+]

First observedSep 16, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false voice. The description adds valuable behavioral context beyond annotations: the first-call refusal flowcars, the prerequisite diagnostics, and the waiver when the baseline closed no trades. This meaningfully informs agent behavior.

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?

The description is compact and the critical prerequisite is front-loaded. The first sentence states the tool's output; the second explains the required session-order constraint. It is slightly dense as a single sentence but contains no filler.

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

Completeness2/5

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

This is a 10-parameter tool with no output schema and low parameter coverage, yet the description only covers prerequisites and a high-level result. It does not explain what a successful response contains, how hypothesis and expected mechanism are used, or how the many optional parameters affect behavior. More context is needed for reliable invocation.

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

Parameters2/5

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

Schema description coverage is only 40% and the description provides no detailed parameter semantics beyond tying the candidate to a hypothesis. It does not explain core fields like changesFromBaseline, candidateSource, similarityThreshold, or priorCandidateSources, so the description fails to compensate for the low schema coverage.

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?

The description identifies the specific action: produce a free-form Pine candidate tied to a hypothesis and expected mechanism. This is reasonably distinct from siblings like verify_candidate or evaluate_candidate, though it does not explicitly name any alternative to distinguish itself from.

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 description gives explicit prerequisites: the first call in a session is refused until inspect_market_context and analyze_losing_trades have succeeded, with a waiver condition. This is clear actionable guidance, though it does not discuss when to prefer this tool over sibling tools.

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

All Algo Trade Analytics 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?