Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testResendConnection

Idempotent

Test a Resend API connection by sending from a specified address to one or more recipients, verifying credentials and sender setup before enabling email notifications.

Instructions

POST /notification.testResendConnection

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": {
      "apiKey": "<apiKey>",
      "fromAddress": "<fromAddress>",
      "toAddresses": "<toAddresses>"
    },
    "name": "notification-testResendConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYes
fromAddressYes
toAddressesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the agent knows this reaches an external service and is repeatable. The description adds nothing beyond that: it doesn't mention that a real message may be dispatched to toAddresses, whether failures surface as errors or return bodies, or whether provider rate limits apply.

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

Conciseness2/5

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

It is a single short token string with no waste, but the brevity comes from under-specification rather than efficiency. Nothing is front-loaded because there is no explanatory content at all.

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

Completeness1/5

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

A three-required-parameter tool that triggers an external, side-effecting send with no output schema needs far more than a route echo. Neither inputs nor the outcome of the test are described, leaving the definition inadequate for correct invocation.

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

Parameters1/5

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

All three parameters (apiKey, fromAddress, toAddresses) are required and schema description coverage is 0%, so the description carries the full burden of explaining them. It says nothing about key format, sender-address verification requirements, or whether the message goes to every entry in toAddresses.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only 'POST /notification.testResendConnection', which restates the tool name as an HTTP route rather than stating what the tool does. It never says a test notification/email is sent through the Resend provider or that it verifies credentials, so the purpose is inferable only from the name and annotations.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no preconditions (e.g. that valid Resend credentials and a verified from-address are required), and no reference to the many sibling test tools for other providers. The agent must guess that this is the Resend-specific variant of a generic connection test.

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

Deploy Server

Other Tools