Skip to main content
Glama
proton-mail-mcp

proton-mail-mcp

by jasen1300

get_ai_policy

Show the active natural-language AI policy to see how AI triage and AI digest behavior is currently configured.

Instructions

Show the current natural-language AI policy (controls ai_triage/ai_digest).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ai_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/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 load; 'Show' and the get_ prefix make the read-only nature clear, and the note that the policy controls ai_triage/ai_digest is genuine behavioral context an agent could not get from schema or annotations. It does not state permissions, size, or whether the returned policy is the effective or stored version.

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?

A single front-loaded sentence with no filler; the purpose and the policy's downstream effect are packed into one clause with zero waste.

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?

An output schema exists, so return values need not be explained, and a zero-parameter read tool needs little more. The only missing piece is the relationship to set_ai_policy, which would let an agent round-trip read-modify-write without guessing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Show') with a specific resource ('the current natural-language AI policy') and adds what the policy governs ('controls ai_triage/ai_digest'), so the agent knows exactly what it retrieves. It stops short of naming set_ai_policy as the mutating counterpart, which is the one sibling distinction worth making.

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 parenthetical that the policy controls ai_triage and ai_digest implies when an agent would want to inspect it before those calls, but there is no explicit when-to-use statement and no pointer to set_ai_policy for changes. Usage is inferable rather than stated.

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