Skip to main content
Glama
Omkar2240

ChaosBull MCP

by Omkar2240
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

simulate_network_drop

Aborts matching browser requests after a delay to simulate a mid-flight connection drop and check whether the app shows fallback UI or degrades gracefully.

Instructions

Opens the browser, navigates to the application, and aborts requests matching a pattern after a delay, simulating a mid-flight connection drop. Use to answer: what happens if the network drops after the order request is sent but before the response arrives?

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the page to test
wait_msNoMilliseconds to wait after navigation before checking fallback (default: 2000)
headlessNoWhether to run in headless mode (default: false, launches real browser so user sees application)
viewportNoViewport size (default: 1280×720)
drop_after_msNoMilliseconds to wait before aborting the request, simulating mid-flight drop (default: 500)
preview_delay_msNoMilliseconds to pause after simulation before closing browser, allowing visual inspection (default: 2000)
fallback_selectorNoCSS selector for the fallback UI that should appear (e.g., '.timeout-error')
intercept_patternYesGlob pattern for requests to drop (e.g., '**/api/order**')
keep_browser_openNoKeep browser window open after test completes so user can interactively inspect the app (default: false)
api_health_check_urlNoOptional backend or hosted API health check URL to verify before running chaos test. Aborts if backend is down or errors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description must carry behavioral disclosure. It explains the core browser automation and request-abort behavior, but omits side effects such as launching a real browser by default, browser lifecycle, fallback assertion behavior, and health-check abort handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly worded sentences: the action sequence is front-loaded and the usage scenario follows. Every clause adds useful meaning with no waste.

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 definition covers what the tool does and a representative use case, and the rich schema covers all ten parameters including nested viewport and timing controls. Some browser lifecycle and result behavior is left implicit, but there is no output schema and the parameter descriptions fill the main gaps.

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 all ten parameters in detail. The description only loosely references a matching pattern and a delay, adding no syntax or semantics beyond the schema.

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?

States a concrete sequence—open browser, navigate, abort matching requests after a delay—and the simulation intent. It does not explicitly name sibling alternatives, so the boundary with tools like simulate_api_failure or trigger_system_network_error must be inferred.

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?

Provides a clear example scenario the tool is meant to answer, giving good selection context. It lacks any when-not-to-use guidance or explicit comparison with alternative chaos tools.

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