Skip to main content
Glama
Sign In
addy-mcp

addy-mcp

by Former-Stranger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

forget_alias

Destructive

Permanently removes an alias from your addy.io account by disassociating it, with no option to restore it afterward.

Instructions

PERMANENTLY forget an alias: it is disassociated from the account and cannot be restored.

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": "forget_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

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description still adds genuine context beyond them by stating the operation is permanent and unrecoverable, which tells the agent the effect outlives the call. It does not say what happens to the alias's recipients or whether the address can be recreated.

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?

A single sentence with the consequence and the irreversibility front-loaded. Nothing is wasted and the most important word arrives first.

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 one-parameter mutation with annotations covering the safety profile and no output schema, the description supplies the key missing fact: the action is irreversible. Only the lack of sibling differentiation (delete_alias vs forget_alias) keeps it from being fully complete.

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?

There is a single required parameter with 100% schema coverage, and the schema already documents alias_id as a UUID. The description adds no meaning about the identifier or its format, so the schema carries the full burden.

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 and resource ("forget an alias") plus the scope of the effect (disassociated from the account). It does not distinguish itself from the sibling delete_alias or explain how "forget" differs from "delete," which matters given restore_alias also exists.

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

Usage Guidelines3/5

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

The word "PERMANENTLY" and "cannot be restored" act as an implicit caution that steers an agent away from casual use, but the description never says when to choose this over delete_alias or restore_alias. Usage is only implied through the irreversibility warning.

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