Skip to main content
Glama
Sign In
mailpouch

mailpouch

by chandshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Request Permission Escalation

request_permission_escalation

Request elevated email permissions by specifying a target preset and detailed reason. A human must approve via the settings UI; poll escalation status for the result.

Instructions

Request an increase in the server's active permission preset. YOU CANNOT APPROVE THIS YOURSELF — approval requires a human to open the settings UI (http://localhost:8766) and click Approve. Use check_escalation_status to poll for the result. Downgrading (reducing access) never requires a challenge.

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": {
      "target_preset": "<target_preset>",
      "reason": "<reason>"
    },
    "name": "request_permission_escalation"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy you need elevated permissions. Shown to the human verbatim. Be specific — vague reasons are more likely to be denied.
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).
target_presetYesThe preset you are requesting. Must be higher than the current preset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}
  2. First observedv3.0.77

TDQS

A5/5.0
Behavior5/5

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

Discloses that approval requires a human action (opening UI and clicking Approve), which is critical behavioral context beyond annotations. It adds the URL and process, and notes the non-self-approvable nature. No contradiction with annotations.

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?

Two sentences containing all essential info: what it does, that agent cannot approve, where to approve, how to poll, and a note about downgrading. Every sentence earns its place; front-loaded with purpose.

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 complexity (requires human approval, polling for result), the description covers the full workflow: request, human approval step, polling. It also addresses downgrading. No output schema needed as the polling tool handles results.

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

Parameters5/5

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

Adds meaningful advice beyond schema: 'Be specific' for reason, 'Omit to use the active account' for account_id, and 'Must be higher than current preset' for target_preset. Schema coverage is 100%, but description provides extra guidance.

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 tool's purpose: requesting an increase in permission preset. It explicitly distinguishes from checking status (check_escalation_status) and notes that downgrading doesn't require this tool. The verb+resource is precise.

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?

Explicitly states when to use: to request higher permissions. It tells the agent it cannot approve and must poll via check_escalation_status. It also clarifies that downgrading never requires a challenge, implying not to use this for reduction.

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