email-spam-tester

Wait for the report

wait_for_report

Read-onlyIdempotent

Wait until the message arrives and has been analysed, then summarise it.

Call it after the email has been sent to the address from
get_test_address. Blocks rather than returning "not ready yet": an agent
told to poll writes a sleep loop and usually gives up before the analysis
finishes. Provider placement keeps filling in for up to 30 minutes after
the report; get_report reads the latest.

Input Schema

Name	Required	Description	Default
`slug`	Yes	The slug get_test_address returned, the last part of the report URL.
`timeout_seconds`	No	How long to block waiting for the message and its analysis, in seconds. The checks are ready in well under a minute; the fix plan takes about another one. Past this the tool returns what it has.

Output Schema

Name	Required	Description	Default
`view`	Yes	Which card to draw.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedOutput schema / properties / view / description

Previous value: -"test, report, mailbox, mailboxes, series or error"New value: +"Which card to draw."

Changed6 schema fields changedSep 30, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / description

Added value: +"What every tool returns for the card; `view` says which card."

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / view

Added value: +{
+  "description": "test, report, mailbox, mailboxes, series or error",
+  "title": "View",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "view"
+]

changedOutput schema / title

Previous value: -"wait_for_reportOutput"New value: +"Output"

Changed4 schema fields changedSep 18, 2026

addedInput schema / properties / slug / description

Added value: +"The slug get_test_address returned, the last part of the report URL."

addedInput schema / properties / timeout_seconds / description

Added value: +"How long to block waiting for the message and its analysis, in seconds. The checks are ready in well under a minute; the fix plan takes about another one. Past this the tool returns what it has."

addedInput schema / properties / timeout_seconds / maximum
```
Added value: +600
```
addedInput schema / properties / timeout_seconds / minimum
```
Added value: +5
```

First observedSep 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say readOnly/idempotent; the description adds the crucial blocking behavior, the 30-minute provider-placement window, and that it returns partial state after timeout. These are exactly the traits an agent cannot learn from the schema or annotations.

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

Conciseness4/5

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

Front-loads the purpose, then rationale, then sibling routing. The polling-explanation sentence is a touch long but its content is load-bearing rather than filler.

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

Completeness5/5

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

An output schema exists, so return shape needs no explanation; the description covers everything else an agent needs: ordering, blocking semantics, timeout behavior, and where to go next (get_report).

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%, so the baseline is 3; the description earns extra by tying slug provenance to get_test_address and clarifying the timeout trade-off (checks under a minute, fix plan ~another minute, then returns what it has). Slight redundancy with the schema's own timeout text.

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?

States a specific verb (wait) and resource (for the message/report), with the added twist that it summarises the analysed message. The polling-vs-blocking distinction and the 'call it after get_test_address' sequencing separate it cleanly from get_report and the other siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit ordering ('Call it after the email has been sent to the address from get_test_address') and an explicit alternative ('get_report reads the latest'), plus a when-not rationale: agents that poll a non-blocking call write sleep loops and give up. Nothing is left to inference.

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

All email-spam-tester tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.