Skip to main content
Glama
Sign In
hotmail-mcp

hotmail-mcp

by oshann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

confirm_restore_rules

Commit a rule restore by deleting current inbox rules and recreating a snapshot's rules, with automatic backup for reversibility.

Instructions

COMMIT a restore previewed by restore_rules. Destructive.

Deletes every current inbox rule and recreates the snapshot's rules. Requires a fresh authentication prompt. Snapshots the current state first, so this is itself reversible via the returned safety_backup_id.

Args: draft_id: The id returned by restore_rules.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "confirm_restore_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, but the description fully discloses that the tool is destructive, deletes all current inbox rules, requires fresh authentication, and creates a safety backup that makes the operation reversible. This is comprehensive behavioral information.

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 concise and well-structured: a one-line summary starting with 'COMMIT...Destructive.', followed by a paragraph explaining effects and requirements, then an 'Args:' section. It is front-loaded and every sentence adds value.

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

Completeness5/5

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

Given the single parameter, no output schema, and no annotations, the description covers the purpose, precondition (draft_id from restore_rules), effects (destructive, backup), and reversibility. It is complete for an agent to understand and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains that `draft_id` is the id returned by `restore_rules`, which adds meaning beyond the schema title 'Draft Id'. Schema coverage is 0%, so this parameter description is beneficial.

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 it commits a restore previewed by `restore_rules`, and explains it deletes current rules and recreates snapshot's rules. This distinguishes it from the sibling `restore_rules` tool.

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

Usage Guidelines4/5

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

It explicitly states it requires a `draft_id` from `restore_rules` and that it is destructive. It implies it is used after a preview, but does not explicitly say when not to use it or list alternatives beyond `restore_rules`.

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