Retrieve recent HTTP or email requests captured by a sandbox endpoint, newest first, to inspect webhook payloads and troubleshoot delivery.
List recent requests captured by a sandbox endpoint, newest first.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Only HTTP requests ("http") or only captured emails ("email") | |
| limit | No | Max requests to return | |
| since | No | Only return requests after this timestamp in ms | |
| endpointSlug | Yes | The endpoint slug |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses sort order (newest first) and that results are scoped to a sandbox endpoint, but says nothing about read-only nature, truncation/limit behavior, pagination, or retention of captured requests.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the verb and resource, with the sort order appended efficiently. Nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description should hint at the shape of a returned request (or at least confirm the list/ordering semantics and any caps), but it does not. Identification of the tool is complete enough to invoke it, but return expectations remain unset.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already explains endpointSlug, kind, limit, and since. The description adds no parameter-level detail (e.g., how 'recent' relates to limit or whether since and limit combine), so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) plus resource (requests captured by a sandbox endpoint) and adds ordering (newest first), which is more than the name conveys. It is inferably distinct from the singular get_request and wait_for_request, though no sibling is named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no when-to-use framing at all — nothing about when to browse the list versus fetching a single request with get_request or blocking with wait_for_request, and no preconditions (endpoint must exist and have captured traffic) are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.