Agent workflow

Test HTTP failure paths safely

Exercise retry, redirect, webhook, and malformed-response handling against bounded fixtures instead of arbitrary infrastructure or production endpoints.

Outcome

Agents can reproduce client behavior using deterministic status responses and clearly synthetic data with published expiry and content limits.

Small context footprint

Use only the needed primitive

Safe execution

Agent workflow

  1. State the exact client behavior to test, such as 429 plus Retry-After.
  2. Search and describe the fixture tool before invocation.
  3. Keep payloads synthetic, bounded, and free of credentials or customer data.
  4. Record the fixture expiry and assert the client result, not merely the returned status.

Connect an agent

Connect the agent to the public Streamable HTTP MCP endpoint, search with the concrete job, and describe only the selected tool before invoking it.

https://liberated.site/mcp

Try this intent

Test whether this webhook client respects a bounded 429 Retry-After response.