Skip to main content
Glama

resume_rule

Destructive

Resumes a paused reply rule with human approval: returns a preview and request ID, then re-enables the rule once approved.

Instructions

Ask for a paused reply rule to be switched on again. A reply rule tells GigaMail that, for mail from the given senders (or arriving in the given folder), it prepares a reply from the listed documents, in the given style, within a daily cap and a cooldown per sender, until the rule expires. In semi mode it prepares each reply and waits for the user's approval; in auto mode it replies without asking, so an auto rule is a standing permission to send mail. TWO-PHASE, HUMAN-APPROVED: the first call (no request_id) executes nothing — it returns status=approval_required with a preview of exactly what would happen and a request_id. A human approves out of band, only at the PC (GigaMail console or CLI, never Telegram); the second call with that request_id executes the payload that was approved (the approved arguments, not the ones passed the second time). Requests expire (default 15 min); identical pending requests are deduplicated; more than 20 requests/hour per tool are refused (status=rate_limited). Every phase is written to the audit log. Resuming is approving the rule again, so it needs the user. The preview shows the whole rule as it will run. The request can be approved only by the user at the PC, with Windows Hello / Touch ID / PIN (never from Telegram or by you). You cannot approve it: show the preview and ask the user to approve it in the GigaMail console, then call again with the request_id. Returns {success, rule_id, state}. A rule that has expired stays expired: use renew_rule for that. To stop a rule use pause_rule, which needs no approval.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "resume_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYesRule id exactly as returned by list_rules (for example 'rule_1a2b3c4d').
request_idNoOmit on the first call. On the first call the tool does NOT execute: it returns status=approval_required, a preview and a request_id. A human must approve that request_id at the PC (GigaMail console or `gigamail approvals approve`, never Telegram). Then call again with the same request_id to execute. The agent cannot approve; repeating the call without approval just returns awaiting_approval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.8

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say destructive/openWorld/non-idempotent; the description goes far beyond them, disclosing the two-phase approval flow, that the approved arguments (not the retried ones) are executed, 15-minute request expiry, deduplication, a 20-requests/hour rate limit with status=rate_limited, audit logging, and that auto mode is a standing permission to send mail — consistent with destructiveHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the two-phase flow, which is good, but the 'human approves only at the PC, never Telegram, you cannot approve' constraint is restated three or four times, and the request-can-be-approved-only sentence is near-duplicated, inflating length without adding information.

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?

For a destructive, approval-gated mutation with no output schema, the description covers everything an agent needs: the two-call protocol, what to show the user, error statuses (rate_limited, awaiting_approval), the return shape {success, rule_id, state}, and the correct sibling for expired rules.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds meaning the schema omits: the second call executes the payload approved by the human, not the arguments passed the second time, and it clarifies what rule_id must reference (a paused rule from list_rules).

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?

Opens with a specific verb+resource ('Ask for a paused reply rule to be switched on again') and immediately follows with what a reply rule is, so an agent understands both the action and the object. It is clearly distinguishable from siblings, which it names: renew_rule for expired rules and pause_rule to stop one.

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

Usage Guidelines5/5

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

Gives explicit routing: use renew_rule when a rule has expired (expired stays expired), use pause_rule to stop a rule and it needs no approval. It also states the prerequisite that a human must approve at the PC, and the procedural when-to-call sequence (first call without request_id, then second call with it).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.