Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

List mail rules

list_mail_rules
Read-onlyIdempotent

Retrieve persistent mail rules with IDs, names, enabled status, conditions, actions, and timestamps to check existing rules before creating, updating, or deleting one.

Instructions

List the persistent mail rules with their ids, names, enabled state, conditions, actions, and creation/modification times. Use this to answer "what rules do I have?", before updating or deleting a rule, or to check whether a similar rule already exists before creating a new one.

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": "list_mail_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, and closed-world, so the safety profile needs no restatement. The description adds real value by specifying the returned fields and noting the rules are persistent, which implicitly tells the agent the list survives across sessions. It does not mention whether an empty list is possible or any ordering, which keeps it short of a 5.

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, the payload description first and the usage routing second. Every clause carries information: the field list tells the agent what it will get, and each of the three usage triggers points at a distinct workflow.

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?

There is no output schema, so the description deliberately enumerates the return fields, which is exactly the right compensation. For a zero-parameter read tool with full annotation coverage, nothing an agent needs before calling it is missing.

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 no parameter meaning to add beyond the schema; the baseline for a param-free tool applies. The description correctly implies an unconditional, unfiltered enumeration rather than suggesting any optional scoping the agent might hunt for.

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?

States a specific verb (list) and resource (persistent mail rules) and enumerates exactly what each entry contains: ids, names, enabled state, conditions, actions, and creation/modification times. An agent can distinguish this from create_mail_rule/update_mail_rule/delete_mail_rule and from the other list_* tools purely from the description.

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 when-to-use triggers: answering 'what rules do I have?', preceding an update or delete, and de-duplicating before a create. Those triggers map directly onto the create/update/delete siblings, so the routing decision is unambiguous rather than inferred.

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