Skip to main content
Glama

race

Conduct race condition testing using burst, single_packet, or staggered timing modes to reveal HTTP synchronization vulnerabilities.

Instructions

Race condition testing with burst, single_packet, and staggered timing modes. See rqwstr_docs(topic="race") for timing-mode guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sniNoTLS SNI override. Decouples SNI from Host header for HTTPS requests.
urlYesTarget URL
bodyNoRequest body
grepNoRegex to search response bodies
nameNoRequest name for result labeling
countNoNumber of copies to send (default 10; ignored when payloads set)
methodYesHTTP method
timingNoTiming mode: burst (default), single_packet (H2 single-frame attack), or staggered_us:N
headersNoRequest headers
payloadsNoDifferent payloads for each request (overrides count)
raw_pathNoSend URL path exactly as provided without Go net/url normalization. Preserves percent-encoded sequences like %2f literally. For web cache deception and path traversal attacks.
body_fileNoRelative path under hunt artifacts directory for request body; absolute paths require RQWSTR_ALLOW_ABSOLUTE_FILE_PATHS=1. Overrides body.
multipartNoMultipart form-data parts. Each part: {name, value, filename, content_type, body_file/file_path}. File paths are relative to hunt artifacts unless RQWSTR_ALLOW_ABSOLUTE_FILE_PATHS=1. Overrides body/body_file.
timeout_msNoPer-request timeout in ms (default 30000)
raw_headersNoRaw headers string (\r\n-separated). Appended after headers map. Allows duplicate headers and non-standard formatting.
session_setupNoChain-like steps to run before each burst. Fetches CSRF tokens and session state. Extracted variables substitute via double-brace syntax. Cookies auto-forward.
payload_markerNoMarker to replace with payload (default {{PAYLOAD}})
request_targetNoOverride request-line target (RFC 7230 §5.3.2 absolute-form)
grep_ignore_caseNoCase insensitive grep
Behavior2/5

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

No annotations are provided, and the description adds minimal behavioral context. It mentions timing modes but does not disclose what happens during testing, output format, or side effects. Most behavioral information must be inferred from the schema.

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?

The description is concise with two sentences, front-loading the purpose. Every sentence adds value, and the reference to documentation is efficient.

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

Completeness2/5

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

Given the complexity of the tool (19 parameters, nested objects, no output schema), the description is insufficient. It lacks details on how to use the tool, what results to expect, and does not compensate for missing output schema or annotations.

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 parameters are already documented. The description mentions timing modes but does not add meaning beyond the schema. 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 clearly states the tool is for race condition testing, specifying timing modes. It distinguishes itself from sibling tools like 'fetch' or 'intruder' by being purpose-built for race conditions.

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 usage for race condition testing but does not explicitly state when to use this tool over alternatives. The reference to rqwstr_docs for timing guidance provides some direction but no exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kjopstad-IT/rqwstr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server