Skip to main content
Glama
Sign In
addy-mcp

addy-mcp

by Former-Stranger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_alias_recipients

Idempotent

Replace the recipients an alias forwards to, optionally set family-member delivery, or use an empty list to restore the default recipient.

Instructions

Replace the set of recipients an alias forwards to.

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>",
      "recipient_ids": "<recipient_ids>"
    },
    "name": "set_alias_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
alias_idYesThe id (UUID) of the item
recipient_idsYesRecipients the alias should forward to (empty list = default recipient)
family_member_idsNoDuo/Family plan member user ids to also deliver to
family_reply_send_idsNoSubset of family_member_ids allowed to reply/send from the alias

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, idempotent, open-world mutation, and the description only restates replacement semantics. It adds no context about permission requirements, atomicity, what happens to previously configured recipients, or how optional family-member parameters interact with replacement.

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 a single front-loaded sentence with no redundant wording. It communicates the core operation efficiently and does not bury the key action.

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

Completeness3/5

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

The schema and annotations carry most of the burden, and the description correctly states the replacement purpose. However, for a mutation tool with a bulk sibling, it omits useful usage context and does not warn about the consequences of replacing recipients, leaving it minimally adequate rather than 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?

Schema description coverage is 100%, so all four parameters and the empty-list default behavior are already documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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?

The description states a specific verb ('Replace') and resource ('the set of recipients an alias forwards to'), making the operation distinguishable from label or option tools. It does not explicitly distinguish the single-alias operation from the sibling bulk_set_alias_recipients, so it falls short of a 5.

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?

The description provides no guidance on when to use this tool versus bulk_set_alias_recipients or related recipient-management tools. It also does not mention prerequisites, side effects, or conditions under which replacement is appropriate.

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