Skip to main content
Glama

MailFixture

by com.mailfixture
OverviewDiscussionsAdmin

list_hook_requests

List requests captured by a hook (id, method, path, content_type, body_size, received_at per request; bodies stay on get_hook_request). Set wait to long-poll for new requests; use since as a cursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoLong-poll up to this many seconds (max 60) for a matching request instead of returning an empty list immediately.
matchNoFilter: `method:POST` (exact verb), `path:term` or `body:term` (substring); a bare term matches the body. Body matching scans the first 32 KiB; detail responses remain complete.
sinceNoOnly requests received after this RFC 3339 timestamp. Use the received_at of the last request you saw as a cursor.
hook_idYesHook id (uuid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Describes return value (request metadata) and key behaviors (long-poll, cursor). With no annotations, it carries the transparency burden; misses details like ordering, pagination limits, or whether response is an array, but is adequate for a simple list.

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 sentences, front-loads core purpose, then usage hints. No redundant words; highly efficient.

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

Completeness3/5

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

No output schema, so description must cover response shape. Lists returned fields and notes body location. Missing ordering, pagination details, and explicit statement that result is an array, but covers essentials.

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%, baseline 3. Description adds context for 'wait' and 'since' beyond schema descriptions (long-poll, cursor usage), enhancing understanding.

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?

Clearly states 'List requests captured by a hook', specifying the verb and resource. Explicitly lists metadata fields returned per request and distinguishes from get_hook_request by noting bodies remain there.

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 guidance on using 'wait' for long-polling and 'since' as a cursor for pagination. However, does not explicitly contrast with sibling tools like wait_for_hook_request or list_hooks.

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

All MailFixture toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources