EmidLabs Backtest

Submit Backtest

submit_backtest

Submits a strategy for backtesting against historical OHLCV data. Returns immediately with an id and status — call get_backtest_result to fetch the outcome once it finishes. Testing the same strategy against many assets? Use submit_backtest_batch instead — one call per asset here adds up fast. Optionally accepts confirmationSources to only count a candidate Entry/Exit as a real trade once corroborated by a submit_confirmation_source result (multi-timeframe or cross-asset confirmation) — see the confirmationSources argument and submit_confirmation_source's own description.

Input Schema

TableJSON Schema

Name	Required	Description
`assetPair`	No	e.g. "BTC-USDC".
`finalDate`	No	ISO date string, e.g. "2025-06-01".
`initialDate`	No	ISO date string, e.g. "2025-01-01".
`backtestApiKey`	No	Your EmidLabs backtest API key (created in the Console). Not needed if this connector was added with a static 'x-api-key' header.
`backtestBaseUrl`	No	Defaults to the public production API. Override only for self-hosted/staging use.
`confirmationSources`	No	Optional. Each entry names a submit_confirmation_source result (same account only, must already be Completed) that every candidate Entry/Exit must be corroborated by before it's simulated as a trade — an unconfirmed candidate is dropped before trade simulation, never appears in get_backtest_trades or affects PnlR/WinRate/etc. See ConfirmedSignalsCount/UnconfirmedSignalsCount on get_backtest_result. A sourceId that doesn't exist, isn't Completed, or belongs to another account fails this submission immediately (unlike live, this is synchronous/batch — letting it through would produce a confusing zero-trade result with no explanation).
`strategySnapshotJson`	No	The Strategy DSL object — every field below documents its own exact shape, this is just the execution model that ties them together. Entry fills at the close of the candle where decision.entry turns true (no lookahead). A position closes on the first of these to happen, checked in this order: stop-loss hit, take-profit hit, decision.exit turning true (a same-candle stop/take-profit always wins over exit). Multiple positions can be open at once by default — cap with configuration.maxOpenPositions. Results are measured in R-units (risk multiples); expectancyR (average R per trade) is the metric to optimize, not raw win rate or trade count.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / strategySnapshotJson / properties / configuration / properties / timezone

Added value: +{
+  "description": "IANA timezone id (e.g. \"America/Sao_Paulo\") used to localize the DSL's hour()/minute()/dayOfWeek()/isWeekend() functions, for time-of-day or weekday gating conditions. Omit/null defaults to \"America/Sao_Paulo\".",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / confirmationSources / items / properties / validityWindow / description

Previous value: -"How recent the source's own signal must be, expressed in candles of the SOURCE's own timeframe — not a fixed duration, so it scales automatically with whichever strategy is confirming."New value: +"An OBJECT, not a bare number — e.g. { \"count\": 5 }. Defaults to { \"count\": 1 } when omitted."

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / confirmationSources

Added value: +{
+  "default": null,
+  "description": "Optional. Each entry names a submit_confirmation_source result (same account only, must already be Completed) that every candidate Entry/Exit must be corroborated by before it's simulated as a trade — an unconfirmed candidate is dropped before trade simulation, never appears in get_backtest_trades or affects PnlR/WinRate/etc. See ConfirmedSignalsCount/UnconfirmedSignalsCount on get_backtest_result. A sourceId that doesn't exist, isn't Completed, or belongs to another account fails this submission immediately (unlike live, this is synchronous/batch — letting it through would produce a confusing zero-trade result with no explanation).",
+  "items": {
+    "description": "One confirmation requirement: this backtest's own candidate Entry/Exit only counts as a trade once sourceId's own signal timeline is corroborated within validityWindow.",
+    "properties": {
+      "signalType": {
+        "description": "\"entry\" or \"exit\" — which of the source's signal types counts as confirming. Defaults to \"entry\" when omitted.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sourceId": {
+        "description": "The id returned by submit_confirmation_source (same account only) whose signal timeline this backtest's candidates must be corroborated by.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "validityWindow": {
+        "description": "How recent the source's own signal must be, expressed in candles of the SOURCE's own timeframe — not a fixed duration, so it scales automatically with whichever strategy is confirming.",
+        "properties": {
+          "count": {
+            "description": "Number of candles of the source's own timeframe. Defaults to 1 when omitted.",
+            "type": "integer"
+          }
+        },
+        "type": [
+          "object",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "sourceId"
+    ],
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

Changed1 schema field changedAug 21, 2026

changedInput schema / properties / strategySnapshotJson / properties / inputs / description

Previous value: -"Named computed values, one JSON-string expression each, evaluated once per candle. Raw fields: close, open, high, low, volume. Built-in functions (case-sensitive, lowercase — no others exist, e.g. avg()/SMA() uppercase/close[N] bracket indexing are NOT supported): ema(series,period), sma(series,period), rsi(series,period), atr(period), adx(period), adxPlusDi(period), adxMinusDi(period), crossUp(a,b), crossDown(a,b), highest(series,n), lowest(series,n), change(series), volumeSma(period), volumeSpike(multiplier), body(), range(), upperWick(), lowerWick(), abs(x), min(a,b), max(a,b). Candlestick patterns (all no-arg, boolean, read only closed-candle OHLC, same in backtest and live): single-candle hammer(), shootingStar(), doji(), bullishMarubozu(), bearishMarubozu(), spinningTop(), dragonflyDoji(), gravestoneDoji(), longLeggedDoji(); two-candle bullishEngulfing(), bearishEngulfing(), piercingLine(), darkCloudCover(), bullishHarami(), bearishHarami(), haramiCross(), tweezerTop(), tweezerBottom(); three-plus-candle morningStar(), eveningStar(), threeWhiteSoldiers(), threeBlackCrows(), threeInsideUp(), threeInsideDown(), threeOutsideUp(), threeOutsideDown(), risingThreeMethods(), fallingThreeMethods(). Caveat: hammer()/shootingStar() are shape-only, no prior-trend check (same shape is Hammer in a downtrend but Hanging Man in an uptrend, and vice versa for shootingStar/Inverted Hammer) — pair with a trend/momentum condition rather than using the shape alone. An input may only reference inputs defined above it (no forward/circular references). Example: {\"emaFast\":\"ema(close, 9)\",\"emaSlow\":\"ema(close, 21)\"}"New value: +"Named computed values, one JSON-string expression each, evaluated once per candle. Raw fields: close, open, high, low, volume. Built-in functions (case-sensitive, lowercase — no others exist, e.g. avg()/SMA() uppercase/close[N] bracket indexing are NOT supported): ema(series,period), sma(series,period), rsi(series,period), atr(period), adx(period), adxPlusDi(period), adxMinusDi(period), crossUp(a,b), crossDown(a,b), highest(series,n), lowest(series,n), change(series), shift(series,n) [look-back only, NaN before enough history], any(boolSeries,n), all(boolSeries,n), count(boolSeries,n) [over the n candles before the current one], swingHigh(series,confirmBars), swingLow(series,confirmBars) [confirmed N-bar swing point, true confirmBars candles AFTER the actual peak/trough — never at the peak itself, so it can't repaint between backtest and live], body(), range(), upperWick(), lowerWick(), isBullish(), isBearish(), abs(x), min(a,b), max(a,b). There is no volumeSma()/volumeSpike() — volume is a plain series like close/open/high/low, so use sma(volume,period) and volume > sma(volume,period) * multiplier instead. Candlestick patterns (all no-arg, boolean, read only closed-candle OHLC, same in backtest and live): single-candle hammer(), shootingStar(), doji(), bullishMarubozu(), bearishMarubozu(), spinningTop(), dragonflyDoji(), gravestoneDoji(), longLeggedDoji(); two-candle bullishEngulfing(), bearishEngulfing(), piercingLine(), darkCloudCover(), bullishHarami(), bearishHarami(), haramiCross(), tweezerTop(), tweezerBottom(); three-plus-candle morningStar(), eveningStar(), threeWhiteSoldiers(), threeBlackCrows(), threeInsideUp(), threeInsideDown(), threeOutsideUp(), threeOutsideDown(), risingThreeMethods(), fallingThreeMethods(). Caveat: hammer()/shootingStar() are shape-only, no prior-trend check (same shape is Hammer in a downtrend but Hanging Man in an uptrend, and vice versa for shootingStar/Inverted Hammer) — pair with a trend/momentum condition rather than using the shape alone. An input may only reference inputs defined above it (no forward/circular references). Example: {\"emaFast\":\"ema(close, 9)\",\"emaSlow\":\"ema(close, 21)\"}"

Changed1 schema field changedAug 20, 2026

changedInput schema / properties / strategySnapshotJson / properties / inputs / description

Previous value: -"Named computed values, one JSON-string expression each, evaluated once per candle. Raw fields: close, open, high, low, volume. Built-in functions (case-sensitive, lowercase — no others exist, e.g. avg()/SMA() uppercase/close[N] bracket indexing are NOT supported): ema(series,period), sma(series,period), rsi(series,period), atr(period), adx(period), adxPlusDi(period), adxMinusDi(period), crossUp(a,b), crossDown(a,b), highest(series,n), lowest(series,n), change(series), volumeSma(period), volumeSpike(multiplier), body(), range(), upperWick(), lowerWick(), abs(x), min(a,b), max(a,b). An input may only reference inputs defined above it (no forward/circular references). Example: {\"emaFast\":\"ema(close, 9)\",\"emaSlow\":\"ema(close, 21)\"}"New value: +"Named computed values, one JSON-string expression each, evaluated once per candle. Raw fields: close, open, high, low, volume. Built-in functions (case-sensitive, lowercase — no others exist, e.g. avg()/SMA() uppercase/close[N] bracket indexing are NOT supported): ema(series,period), sma(series,period), rsi(series,period), atr(period), adx(period), adxPlusDi(period), adxMinusDi(period), crossUp(a,b), crossDown(a,b), highest(series,n), lowest(series,n), change(series), volumeSma(period), volumeSpike(multiplier), body(), range(), upperWick(), lowerWick(), abs(x), min(a,b), max(a,b). Candlestick patterns (all no-arg, boolean, read only closed-candle OHLC, same in backtest and live): single-candle hammer(), shootingStar(), doji(), bullishMarubozu(), bearishMarubozu(), spinningTop(), dragonflyDoji(), gravestoneDoji(), longLeggedDoji(); two-candle bullishEngulfing(), bearishEngulfing(), piercingLine(), darkCloudCover(), bullishHarami(), bearishHarami(), haramiCross(), tweezerTop(), tweezerBottom(); three-plus-candle morningStar(), eveningStar(), threeWhiteSoldiers(), threeBlackCrows(), threeInsideUp(), threeInsideDown(), threeOutsideUp(), threeOutsideDown(), risingThreeMethods(), fallingThreeMethods(). Caveat: hammer()/shootingStar() are shape-only, no prior-trend check (same shape is Hammer in a downtrend but Hanging Man in an uptrend, and vice versa for shootingStar/Inverted Hammer) — pair with a trend/momentum condition rather than using the shape alone. An input may only reference inputs defined above it (no forward/circular references). Example: {\"emaFast\":\"ema(close, 9)\",\"emaSlow\":\"ema(close, 21)\"}"

Changed2 schema fields changedAug 19, 2026

addedInput schema / properties / strategySnapshotJson / properties / configuration / properties / entryFeePct

Added value: +{
+  "description": "Simulated exchange fee on entry, as a percent (e.g. 0.1 = 0.1%). Omit/null = 0 (no fee, backward compatible). Subtracted from every trade's pnlR/pnlPct so results are net-of-fee by construction. 0-5 range. See the pnlR/expectancyR field descriptions on get_backtest_result for the R-vs-% caveat once a fee is set.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedInput schema / properties / strategySnapshotJson / properties / configuration / properties / exitFeePct

Added value: +{
+  "description": "Simulated exchange fee on exit, as a percent (e.g. 0.1 = 0.1%). Same semantics as EntryFeePct — real exchanges can charge different maker/taker rates per leg, so this is independent, not assumed equal.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

Changed18 schema fields changedAug 7, 2026
- addedInput schema / properties / assetPair / default
```
Added value: +null
```
- changedInput schema / properties / assetPair / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedInput schema / properties / finalDate / default
```
Added value: +null
```
- changedInput schema / properties / finalDate / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedInput schema / properties / initialDate / default
```
Added value: +null
```
- changedInput schema / properties / initialDate / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedInput schema / properties / strategySnapshotJson / default
```
Added value: +null
```
- changedInput schema / properties / strategySnapshotJson / properties / conditions / additionalProperties / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / conditions / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / configuration / properties / timeframe / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / configuration / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / decision / properties / entry / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / decision / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / inputs / additionalProperties / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / inputs / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / properties / score / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedInput schema / properties / strategySnapshotJson / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- removedInput schema / required
```
Removed value: -[
-  "assetPair",
-  "initialDate",
-  "finalDate",
-  "strategySnapshotJson"
-]
```
Changed1 schema field changedAug 6, 2026
- changedInput schema / properties / strategySnapshotJson / properties / configuration / properties / timeframe / description
```
Previous value: -"One of \"15M\", \"30M\", \"1H\", \"2H\", \"4H\", \"1D\"."New value: +"One of \"5M\", \"15M\", \"30M\", \"1H\", \"2H\", \"4H\", \"1D\"."
```

Changed7 schema fields changedJul 29, 2026

changedInput schema / properties / strategySnapshotJson / description

Previous value: -"The Strategy DSL object — see the strategy-dsl-spec resource for the shape."New value: +"The Strategy DSL object — every field below documents its own exact shape, this is just the execution model that ties them together. Entry fills at the close of the candle where decision.entry turns true (no lookahead). A position closes on the first of these to happen, checked in this order: stop-loss hit, take-profit hit, decision.exit turning true (a same-candle stop/take-profit always wins over exit). Multiple positions can be open at once by default — cap with configuration.maxOpenPositions. Results are measured in R-units (risk multiples); expectancyR (average R per trade) is the metric to optimize, not raw win rate or trade count."

addedInput schema / properties / strategySnapshotJson / properties / conditions / description

Added value: +"Named boolean expressions over inputs/market data. Operators: > < >= <= == != AND OR. Example: {\"trendUp\":\"emaFast > emaSlow AND adx14 > 20\"}"

changedInput schema / properties / strategySnapshotJson / properties / configuration / properties / direction / description

Previous value: -"\"long\" or \"short\". Defaults to \"long\"."New value: +"\"long\" or \"short\" — picks which side the WHOLE backtest trades, not a mix. Only affects stop-loss/take-profit price placement and the profit/loss sign (mirrored for short: stop above entry, take below entry, profit when price falls) — conditions/score/decision keep the exact same meaning either way. Defaults to \"long\"."

changedInput schema / properties / strategySnapshotJson / properties / decision / properties / exit / description

Previous value: -"Optional boolean expression; closes an open position when true."New value: +"Optional boolean expression; closes an open position when true, independent of riskManagement. If a candle's stop-loss/take-profit and \"exit\" would both trigger, the stop-loss/take-profit wins and exit is not evaluated for that position that candle. If omitted, positions only close via stop-loss/take-profit."

addedInput schema / properties / strategySnapshotJson / properties / inputs / description

Added value: +"Named computed values, one JSON-string expression each, evaluated once per candle. Raw fields: close, open, high, low, volume. Built-in functions (case-sensitive, lowercase — no others exist, e.g. avg()/SMA() uppercase/close[N] bracket indexing are NOT supported): ema(series,period), sma(series,period), rsi(series,period), atr(period), adx(period), adxPlusDi(period), adxMinusDi(period), crossUp(a,b), crossDown(a,b), highest(series,n), lowest(series,n), change(series), volumeSma(period), volumeSpike(multiplier), body(), range(), upperWick(), lowerWick(), abs(x), min(a,b), max(a,b). An input may only reference inputs defined above it (no forward/circular references). Example: {\"emaFast\":\"ema(close, 9)\",\"emaSlow\":\"ema(close, 21)\"}"

addedInput schema / properties / strategySnapshotJson / properties / riskManagement / description

Added value: +"Configures stop-loss/take-profit. Omit entirely for the default (1% stop-loss, 1:3 risk-reward take-profit) — see stopLoss/takeProfit below for the full shape of each."

addedInput schema / properties / strategySnapshotJson / properties / score / description

Added value: +"Integer weight per condition name (keys must match \"conditions\"). The engine sums the weights of every true condition on a candle; compare the total against a threshold in \"decision.entry\" (e.g. \"score >= 50\")."

Changed8 schema fields changedJul 29, 2026

removedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / stopLoss / anyOf

Removed value: -[
-  {
-    "properties": {
-      "percent": {
-        "description": "Stop distance as a percentage of entry price, e.g. 1.0 for 1%.",
-        "type": "number"
-      },
-      "type": {
-        "const": "percent"
-      }
-    }
-  },
-  {
-    "properties": {
-      "multiplier": {
-        "type": "number"
-      },
-      "period": {
-        "type": "integer"
-      },
-      "type": {
-        "const": "atr"
-      }
-    }
-  }
-]

addedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / stopLoss / description

Added value: +"Stop-loss policy. Exactly one of: {\"type\":\"percent\",\"percent\":<number, e.g. 1.0 for 1%>} or {\"type\":\"atr\",\"period\":<int>,\"multiplier\":<number>}. \"type\" is required; field order does not matter."

removedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / stopLoss / required
```
Removed value: -[
-  "type"
-]
```
removedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / stopLoss / type
```
Removed value: -[
-  "object",
-  "null"
-]
```

removedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / takeProfit / anyOf

Removed value: -[
-  {
-    "properties": {
-      "multiple": {
-        "type": "number"
-      },
-      "type": {
-        "const": "riskReward"
-      }
-    }
-  },
-  {
-    "properties": {
-      "percent": {
-        "type": "number"
-      },
-      "type": {
-        "const": "percent"
-      }
-    }
-  }
-]

addedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / takeProfit / description

Added value: +"Take-profit policy. Exactly one of: {\"type\":\"riskReward\",\"multiple\":<number>} (distance = stop-loss distance * multiple) or {\"type\":\"percent\",\"percent\":<number>}. \"type\" is required; field order does not matter."

removedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / takeProfit / required
```
Removed value: -[
-  "type"
-]
```
removedInput schema / properties / strategySnapshotJson / properties / riskManagement / properties / takeProfit / type
```
Removed value: -[
-  "object",
-  "null"
-]
```

Changed4 schema fields changedJul 28, 2026

addedInput schema / properties / backtestApiKey / default
```
Added value: +null
```

changedInput schema / properties / backtestApiKey / description

Previous value: -"Your EmidLabs backtest API key (created in the Console)."New value: +"Your EmidLabs backtest API key (created in the Console). Not needed if this connector was added with a static 'x-api-key' header."

changedInput schema / properties / backtestApiKey / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedInput schema / required

Previous value: -[
-  "backtestApiKey",
-  "assetPair",
-  "initialDate",
-  "finalDate",
-  "strategySnapshotJson"
-]New value: +[
+  "assetPair",
+  "initialDate",
+  "finalDate",
+  "strategySnapshotJson"
+]

First observedJul 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations are all false and convey no safety profile, so the description carries the burden. It discloses asynchronous behavior ('Returns immediately with an id and status'), points to the polling pattern, and details confirmation-source validation semantics (unconfirmed candidates dropped, invalid sourceId fails submission immediately). This is meaningful behavioral context beyond the annotations, though it stops short of discussing rate limits or duplicate-submission effects.

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 a few focused sentences, each earning its place: core purpose, async result flow, batch alternative, and confirmationSources usage. It is front-loaded with the main action and remains scannable despite the somewhat long confirmation-sources sentence.

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?

The tool is complex with 7 parameters and a large strategy DSL schema, but the schema and output schema carry the detailed documentation. The description adds the orchestration context an agent needs: poll get_backtest_result, use the batch variant for many assets, and use confirmation sources for cross-validation. A minor gap is not flagging that strategySnapshotJson is effectively required despite being nullable in the schema.

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 description coverage is 100%, so the schema already documents every parameter in extensive detail. The tool description adds only the cross-tool pointer to submit_confirmation_source and a 'multi-timeframe or cross-asset confirmation' gloss; it doesn't add syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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 'Submits a strategy for backtesting against historical OHLCV data,' naming the action and resource precisely. It explicitly distinguishes itself from submit_backtest_batch and get_backtest_result, so an agent can tell them apart without opening any schema.

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

Usage Guidelines5/5

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

It explicitly says to use submit_backtest_batch instead when testing the same strategy against many assets, and directs the caller to get_backtest_result to fetch the outcome. It also explains the confirmationSources prerequisite via submit_confirmation_source, giving clear when-to-use and alternative guidance.

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

All EmidLabs Backtest tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool maps to a distinct resource and action: submitting/fetching backtests, fetching batch results, fetching trades, submitting/fetching confirmation sources, fetching signals, and listing available assets. The singular vs. batch result tools are explicitly cross-referenced and serve different call patterns, so an agent shouldn't confuse them.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: submit_*, get_*, and list_*. Resource names are clear and predictable, such as backtest, backtest_batch, backtest_trades, confirmation_source, and confirmation_source_signals. The list_/get_ verb variation is conventional and not confusing.

Tool Count5/5

Nine tools is well-scoped for this domain, covering single and batch backtests, result and trade retrieval, asset discovery, and the confirmation-source workflow. Each tool has a distinct role, and none feel like filler or duplication.

Completeness5/5

The tool set covers the full backtesting lifecycle: submit single/batch, fetch aggregate results, fetch trade detail, list available assets, and submit/fetch confirmation sources plus their signals. The confirmation-source workflow integrates cleanly with submit_backtest, and there are no dead ends or obvious missing operations.

Resources

Need Help?