Skip to main content
Glama

chain

Execute multi-step HTTP request chains with variable extraction between steps. Automate complex flows like login sequences with retry and conditional logic.

Instructions

Execute multi-step request chain with variable extraction between steps. Each extract value is a PLAIN STRING pattern (body regex / cookie:name / header:Name:regex), never a nested object like {"type":"json",...}. See rqwstr_docs(topic="chain") for patterns. Preferred path for authenticated flows: forward_cookies (default true) auto-forwards Set-Cookie between steps — see rqwstr_docs(topic="cookies").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsYesOrdered list of request steps
timeout_msNoPer-step timeout in milliseconds (default 30000)
stop_on_errorNoStop chain on non-2xx response
forward_cookiesNoAuto-forward Set-Cookie headers between steps (default true)
single_connectionNoReuse same TCP connection across all steps (for connection-state attacks)
stop_on_missing_varNoStop if {{VAR}} references undefined variable
stop_on_extract_failNoStop if extraction finds no match
Behavior4/5

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

With no annotations, the description carries full disclosure burden. It details extraction pattern formats, default forward_cookies behavior, first-document-wins for SSE, and references docs for patterns. However, it omits error handling nuances and rate limit/authentication requirements.

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

Conciseness3/5

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

The description is front-loaded with the main purpose but includes redundant explanations (e.g., extract patterns repeated). It could be more concise without losing key information.

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?

Despite the tool's complexity (multi-step chain with variable extraction), the description does not explain the return value or response format. With no output schema, the agent remains uninformed about what the tool yields, a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds critical semantics for the extract parameter: it explicitly prohibits nested objects, explains pattern forms, and clarifies edge cases like SSE unwrapping. This goes beyond the schema's description of 'plain string pattern'.

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 executes a multi-step request chain with variable extraction, distinguishing it from single-request siblings like fetch and send. It uses specific verb 'Execute' and resource 'multi-step request chain', and the sibling list confirms its uniqueness.

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 to use forward_cookies for authenticated flows but does not explicitly contrast with alternatives or state when not to use the tool. No guidance on choosing between chain and other tools like race or parallel is provided.

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