Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

set_ai_policy

Set a free-text AI policy that controls ai_triage and ai_digest, letting you define routing and priority rules in plain language without fixed categories.

Instructions

Set the AI policy as free text (policy_text) - it fully controls ai_triage/ai_digest, without fixed categories.

Example: "Delivery services -> archive. Invoices -> label 'Finance'.
Landlord -> keep, highest priority."

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": {
      "policy_text": "<policy_text>"
    },
    "name": "set_ai_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the free-text policy fully controls ai_triage/ai_digest and has no fixed categories, but it does not clarify whether setting a new policy replaces the existing one, validation constraints, or required permissions.

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 two short sentences plus an example, with the core purpose front-loaded. Every part contributes useful meaning, and the example clarifies the expected natural-language format.

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 simple one-parameter setter with an output schema, the description provides enough information to understand purpose, format, and downstream effect. The main remaining gap is whether the operation overwrites an existing policy, which is not stated.

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 description coverage is 0%, so the description must compensate for the single policy_text parameter. It does this well by stating the parameter is free text, explaining that it fully controls behavior without fixed categories, and giving a concrete routing example.

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 states a specific verb and resource: 'Set the AI policy as free text (policy_text)'. It also explains downstream scope by saying the policy fully controls ai_triage/ai_digest, which distinguishes it from the sibling get_ai_policy reader.

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 when to use it by explaining that the policy controls ai_triage and ai_digest. However, it gives no explicit guidance on alternatives, such as using get_ai_policy to inspect the current policy before setting it, and no when-not-to-use conditions.

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