Skip to main content
Glama

crashtestyourstrategy

Challenge a strategy: find what breaks it (3-layer output)

challenge_strategy
Read-onlyIdempotent

USE WHEN you want to know which market regimes break a strategy (buy_and_hold or rsi_30_70) and why. Adversarial evaluation in 3 layers: (1) outcome metrics in the worst regimes, (2) a vulnerability profile over 8 dimensions with severity, (3) the regime descriptors that couple most strongly to failure. Only strategies in the pre-computed outcome matrix can be challenged: 'buy_and_hold' and 'rsi_30_70' ('-' accepted for '_'). asset (optional) limits the worst-regime list to one catalogue asset; the vulnerability profile still spans all 63 regimes. Other strategies: tier2_stress_test (full tier, needs an access token). Vocabulary: ontology://strategy-vulnerabilities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "challenge_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoOptional: list worst regimes of this catalogue asset only (SPY, QQQ, GOLD, BTC, ETH, WTI, VIX; aliases GLD, BTC-USD). VIX has three historical regimes and no synthetic ones. Default: all assets.
strategy_idNoStrategy id from the outcome matrix: 'buy_and_hold' (default) or 'rsi_30_70'. '-' and '_' are interchangeable.buy_and_hold

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asset / description
      Previous value: -"Optional: list worst regimes of this catalogue asset only (SPY, QQQ, GOLD, BTC, ETH, WTI; aliases GLD, BTC-USD). Default: all assets."New value: +"Optional: list worst regimes of this catalogue asset only (SPY, QQQ, GOLD, BTC, ETH, WTI, VIX; aliases GLD, BTC-USD). VIX has three historical regimes and no synthetic ones. Default: all assets."
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / asset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional: list worst regimes of this catalogue asset only (SPY, QQQ, GOLD, BTC, ETH, WTI; aliases GLD, BTC-USD). Default: all assets.",
      +  "title": "Asset"
      +}
    • changedInput schema / properties / strategy_id / description
      Previous value: -"Strategy identifier; v1 supports only 'buy_and_hold'."New value: +"Strategy id from the outcome matrix: 'buy_and_hold' (default) or 'rsi_30_70'. '-' and '_' are interchangeable."
  3. Changed1 schema field changed
    • addedInput schema / properties / strategy_id / description
      Added value: +"Strategy identifier; v1 supports only 'buy_and_hold'."
  4. 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 read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description still adds non-obvious behavior: the asset filter narrows only the worst-regime list while the vulnerability profile spans all 63 regimes, plus the id-normalization rule and a vocabulary resource pointer.

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?

Front-loaded with the trigger condition and then structured as a numbered 1-2-3 breakdown of output layers, which is easy to scan. It is dense as a single block and repeats the strategy-id constraint twice (prose and schema), costing a little efficiency.

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

Completeness5/5

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

Output schema exists so return values need no explanation, annotations cover the safety profile, and both parameters are fully documented. What remains — eligibility, layer structure, and the asset-scope caveat — is exactly what the description supplies.

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 100% and the schema already documents asset aliases, VIX's regime limitation, and the '-'/'_' interchangeability. The description restates the asset scoping caveat but adds little parameter syntax beyond what is already structured, so baseline 3 applies.

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?

Opens with a specific verb+resource ('adversarial evaluation' of a strategy) and enumerates the exact 3-layer deliverable. It also names the sibling it is not (tier2_stress_test), so an agent can distinguish it 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?

Starts with an explicit 'USE WHEN' clause, then states a hard eligibility constraint ('only strategies in the pre-computed outcome matrix') and routes the out-of-scope case to tier2_stress_test with the reason (needs an access token). Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.