Skip to main content
Glama
Sign In

Nextmail

by sh.nextmail
OverviewDiscussionsAdmin

Discard webhook dead letter

discardWebhookDeadLetter
Destructive

Close one open dead letter of a webhook endpoint without sending it. The event stays in the delivery log, where replayWebhookDelivery can still send it. Confirm with the person before calling it. One that was replayed cannot be discarded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpointId": "<endpointId>",
      "deadLetterId": "<deadLetterId>"
    },
    "name": "discardWebhookDeadLetter"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpointIdYesThe webhook endpoint, by its id (whe_…). listWebhooks names every one.
deadLetterIdYesA dead letter of this endpoint, by its id (dlq_…). listWebhookDeadLetters names them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds that this does not send the event, that the event remains in the delivery log, that replay remains possible, and that replayed dead letters cannot be discarded. It also says to confirm with the person, adding safety context beyond annotations.

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?

Four short sentences, front-loaded with the action and scope; each sentence carries operational information (no-send, replay availability, confirmation, replayed exclusion). There is no repetition or 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?

For a two-parameter destructive tool with full schema coverage, no output schema, and annotations declaring destructiveness, the description supplies the missing operational context: what is closed, what remains, replay semantics, confirmation, and exclusion. Nothing an agent needs to invoke it correctly is absent.

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

Parameters3/5

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

Schema has 100% description coverage for both required parameters (endpointId, deadLetterId), including id prefixes and list tools. The description adds no parameter-specific syntax or constraints beyond identifying 'one open dead letter of a webhook endpoint,' so the baseline 3 applies.

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?

Names a specific verb (Close/discard) and resource (one open dead letter of a webhook endpoint), and explicitly separates itself from sending by saying 'without sending it.' It also distinguishes the action from replayWebhookDelivery by explaining that the event remains available for replay.

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?

Provides when-to-use (close an open dead letter without sending), when-not (a replayed one cannot be discarded), and an alternative path (replayWebhookDelivery can still send it). It also adds a confirmation requirement before calling.

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

All Nextmail toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources