Skip to main content
Glama

crashtestyourstrategy

Run stress test (buy-and-hold, v1)

run_stress_test
Read-onlyIdempotent

USE WHEN you want buy-and-hold stressed against one named synthetic regime. Returns a 0-100 robustness score, failure-behaviour classification with confidence and the resolved regime parameters. Evaluates buy-and-hold only and takes exactly one argument, profile_hint (valid values: get_started); for other strategies use challenge_strategy or tier2_stress_test (full tier, needs an access token). Descriptive, not advisory.

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": {
      "profile_hint": "<profile_hint>"
    },
    "name": "run_stress_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_hintYesSynthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Valid values are listed by get_started (profile_hints) and the regimes://available resource.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / profile_hint / description
      Previous value: -"Synthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Discover valid values via the regimes://available resource."New value: +"Synthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Valid values are listed by get_started (profile_hints) and the regimes://available resource."
  2. Changed1 schema field changed
    • addedInput schema / properties / profile_hint / description
      Added value: +"Synthetic stress-regime identifier, e.g. 'whipsaw_synthetic_spy'. Discover valid values via the regimes://available resource."
  3. 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 readOnly, idempotent, closed-world and non-destructive, so the safety profile is not the description's burden. The description adds useful context beyond them: what is returned (0-100 robustness score, failure classification with confidence, resolved regime parameters) and the 'descriptive, not advisory' framing. It omits rate limits or cost, which keeps it short of a 5.

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?

Dense single paragraph with the trigger clause, scope, outputs, alternative routing and argument note all front-loaded. Each clause earns its place, though the argument parenthetical reads awkwardly and could be tightened.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them. Scope, the single argument, token requirements for the alternative tier, and the descriptive stance are all present for a one-parameter read-only tool.

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%, so the parameter is already documented and the baseline is 3. The description's 'valid values: get_started' is ambiguous — it is unclear whether get_started is the sole legal value or a pointer to where values are listed, which the schema resolves but the description muddies.

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 verb and scope: buy-and-hold stressed against exactly one named synthetic regime. It explicitly bounds the tool to buy-and-hold only, which separates it from the sibling strategy-stress tools without needing their schemas.

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?

Opens with an explicit 'USE WHEN' trigger and names concrete alternatives (challenge_strategy for other strategies, tier2_stress_test for the full tier) along with the token prerequisite for the latter. Both the when and the when-not 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.