Skip to main content
Glama
Sign In
deep-agentic-core-mcp

deep-agentic-core-mcp

Official
by DeepAgentLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Run Chaos Experiment

chaos.run_experiment
Destructive

Run a sandboxed target script under selected chaos faults, enforce allow/deny glob policy, and report resulting events plus AI Operations run conformance.

Instructions

Run a workspace-sandboxed target script under selected chaos faults and report the resulting events. The script must also pass the configured allow/deny glob policy. With agentic-chaos>=0.5.1 the result includes an AI Operations v0.4-draft run artifact and its conformance check.

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": {
      "script": "<script>",
      "faults": "<faults>"
    },
    "name": "chaos.run_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
faultsYes
scriptYesScript path, resolved inside the workspace root.
session_idNoSession to read/write shared state under. Defaults to 'default'.
export_aiosNoAttach an AIOS run export (`aios_run`). Defaults to true.
workflow_idNoExternal Workflow ID for the export's run-of link.
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.5
    • addedInput schema / properties / export_aios
      Added value: +{
+  "description": "Attach an AIOS run export (`aios_run`). Defaults to true.",
+  "type": "boolean"
+}
    • addedInput schema / properties / workflow_id
      Added value: +{
+  "description": "External Workflow ID for the export's run-of link.",
+  "type": "string"
+}
  2. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnly=false, openWorld=true and destructive=true; the description usefully adds that execution is workspace-sandboxed, gated by an allow/deny glob policy, and that output depends on the agentic-chaos version. It does not say what the script can destroy or the consequence of a failing conformance check, but with annotations carrying the safety profile this is solid added context.

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?

Three sentences with the core action front-loaded and the policy prerequisite immediately after. No filler, though the version-conditional artifact sentence is somewhat tangential.

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 destructive 6-parameter tool with no output schema and no enums, the description covers the execution model, sandboxing, policy gate, and output artifact well enough to call it correctly. Minor gaps remain around timeout behavior and session-state effects.

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 67% and the description reinforces script resolution (workspace root), fault selection, and the export_aios behavior (attaching an AI Operations artifact). It says nothing about session_id, workflow_id, or timeout_seconds, so it only partially compensates for the coverage gap.

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 (Run) and resource (a workspace-sandboxed target script under chaos faults), plus the outcome (report resulting events). It is clearly distinct from siblings like chaos.list_faults and chaos.export_aios_run, so an agent can route to it without opening a schema.

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

Usage Guidelines3/5

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

The description implies when the tool applies (executing a script under injected faults) and gives one prerequisite (passing the allow/deny glob policy), but never states when to prefer it over alternatives such as chaos.list_faults or when not to run an experiment. Usage is inferred rather than specified.

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

Deploy Server

Other Tools