Skip to main content
Glama

list_rules

Read-onlyIdempotent

List your reply rules to see which senders or folders trigger automatic or semi-automatic replies, including mode, state, limits and expiry. Read-only, no mail is read or sent.

Instructions

List the user's reply rules, newest first.

A reply rule tells GigaMail that, for mail from given senders or
arriving in a given folder, it prepares a reply (`semi`) or sends it
without asking (`auto`). Returns, per rule: rule_id, account_id,
trigger_kind ('senders' | 'folder'), trigger_values, mode, first_contact,
reply_style (the instruction), doc_paths, attachments, cc, daily_cap,
cooldown_hours, expiry_days, expires_at (unix time), state ('active' |
'paused' | 'expired'), expiring (true in the last days before expiry),
pause_reason, sent_today. Read-only and local: no mail is read or sent.
Use the rule_id with rule_activity, pause_rule, update_rule,
resume_rule, renew_rule or delete_rule.

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_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.8

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and closed-world scope, so the safety profile is covered. The description adds a modest clarification ('local: no mail is read or sent'), but then spends most of its length enumerating return fields that the output schema already documents, so the net behavioral value beyond structured data is limited.

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?

The key scoping and ordering statement is front-loaded and the trailing tool-routing sentence earns its place. However, the long comma-separated field inventory (rule_id through sent_today) largely restates the output schema and inflates the description without adding call-relevant guidance.

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 zero-parameter, read-only listing tool with full annotations and an output schema, the description supplies everything needed: what a rule is, mode semantics, state values, and which tools to chain into. Nothing required to call it correctly 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 and the schema is fully described, so there is nothing for the description to compensate for. It correctly adds no parameter prose, keeping the call shape unambiguous.

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 first sentence names a specific verb and resource ('List the user's reply rules') and adds an ordering guarantee ('newest first'). The follow-up sentence defines what a reply rule is and what 'semi' vs 'auto' mean, so an agent can distinguish this from rule_activity or list_messages without opening a schema.

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

Usage Guidelines4/5

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

It routes follow-up work explicitly by naming the tools that consume rule_id (rule_activity, pause_rule, update_rule, resume_rule, renew_rule, delete_rule), which tells the agent this is the discovery step before any rule mutation. It stops short of stating when not to use it or contrasting with any alternative listing tool.

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