Skip to main content
Glama
Sign In
addy-mcp

addy-mcp

by Former-Stranger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

restore_alias

Restore a deleted alias using its UUID to make it active again in your addy.io account.

Instructions

Restore a deleted alias.

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": {
      "alias_id": "<alias_id>"
    },
    "name": "restore_alias"
  }
}

Input Schema

NameRequiredDescriptionDefault
alias_idYesThe id (UUID) of the item

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this is a non-destructive write. The description adds nothing beyond that: no permission requirements, no statement of whether restored aliases retain recipients/labels, and no failure modes for expired or non-deleted IDs.

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?

One short, front-loaded sentence with zero waste, though it is arguably too terse for a mutation tool. Structurally clean.

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

Completeness2/5

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

For a mutation tool with no output schema and no added behavioral detail, the description omits recovery-window limits, permission needs, and what exactly gets restored. An agent can pick the tool but cannot anticipate its outcomes.

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 coverage is 100% and the single alias_id parameter is documented as a UUID, so the schema carries the load. The description adds no nuance, such as that the ID must refer to a deleted alias rather than a live one; baseline 3 applies.

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

Purpose4/5

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

States a specific verb (restore) and resource (a deleted alias), which distinguishes it from delete_alias, forget_alias and create_alias by naming the recovery action. It lacks explicit sibling differentiation, but 'deleted' scopes the operation clearly.

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?

No when-to-use guidance versus alternatives such as recreating the alias with create_alias or the bulk_alias_action sibling. It implies undoing a deletion but states no preconditions, such as whether the alias must still be recoverable.

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