Skip to main content
Glama
Sign In
@emailalias/mcp

@emailalias/mcp

by emailalias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_destination

Add a new email forwarding destination. Sends a verification email; the destination only becomes active after the recipient clicks the link.

Instructions

Add a new forwarding destination. Triggers a verification email to that address; the destination is unusable until the recipient clicks the link. Premium feature.

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": {
      "email": "<email>"
    },
    "name": "add_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.5/5.0
Behavior4/5

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

Discloses a key side effect (triggers verification email) and states the destination is unusable until link clicked. Since no annotations exist, this info carries the full burden and is fairly transparent, though it doesn't cover error handling or other effects.

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?

The description is brief and directly to the point, with no fluff or redundancy. It efficiently conveys the essential action and outcomes.

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

Completeness4/5

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

For a single-parameter tool with no output schema, the description covers the main action and its immediate consequence (verification). It could mention what happens after clicking the link or any return value, but the context is adequately complete.

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?

The description does not mention the 'email' parameter at all. With 0% schema coverage, the description fails to compensate by explaining the parameter's purpose or constraints beyond the schema's type/format.

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 the action ('Add a new forwarding destination') with a specific object. It is distinct from sibling tools like delete_destination or list_destinations.

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?

Does not specify when to use this tool versus alternatives. The mention of 'Premium feature' implies a prerequisite but lacks explicit guidance on usage scenarios or conditions.

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