Skip to main content
Glama
Sign In
shipmail-mcp

shipmail-mcp

by shipmail-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Revoke Mailbox App Password

shipmail_revoke_mailbox_app_password
DestructiveIdempotent

Permanently revoke a mailbox app password to immediately terminate access for the associated client.

Instructions

Permanently revoke one mailbox app password. The associated client will lose access immediately.

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": {
      "id": "<id>",
      "app_password_id": "<app_password_id>"
    },
    "name": "shipmail_revoke_mailbox_app_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMailbox ID.
app_password_idYesApp password ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.10

TDQS

A4/5.0
Behavior4/5

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

The description adds value beyond annotations by stating the revocation is permanent and the client loses access immediately. While annotations already indicate destructiveness, the description clarifies the impact. It does not mention idempotency or error states, but the idempotentHint=true annotation covers that aspect.

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, well-structured sentence that conveys the essential information immediately. No unnecessary words or redundancy.

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-action revoke tool with two required parameters and an output schema, the description is sufficient to explain the core functionality and immediate effect. It lacks mention of error conditions or prerequisites, but the simplicity of the tool makes it adequate.

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?

The input schema already provides full descriptions for both parameters (id and app_password_id), covering 100% of schema description. The tool description does not add further parameter-specific semantics, which is acceptable given the schema's thoroughness. Baseline 3 is appropriate.

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?

The description clearly states the action ('permanently revoke') and the resource ('one mailbox app password'). It also specifies the consequence ('associated client will lose access immediately'), making it easy for an agent to understand the tool's purpose and distinguish it from sibling tools like create or list.

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 description implies the tool is used when an app password needs to be revoked, but it does not explicitly provide context on when to use this tool versus alternatives (e.g., deleting mailbox, resetting password). No exclusion criteria or prerequisites are mentioned, though the general usage is clear.

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