Skip to main content
Glama

automation_status

Read-onlyIdempotent

Check if GigaMail's rules watcher is running and count active, paused, and expired rules to confirm new mail is being processed.

Instructions

Say whether the rules watcher is running and how many rules there are.

The watcher is the separate GigaMail process that applies the rules to
new mail: with it stopped no rule does anything. Returns {watcher:
{running, pid, interval (seconds), last_tick_age_seconds, active_rules,
...}, rules: {active, paused, expired, expiring: [rule_id, ...]}}.
Read-only and local. There is no tool to start or stop the watcher: the
user does that from the GigaMail console.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.8

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it explains the watcher's role in the system, the consequence of it being stopped, and the exact return structure including tick age and expiring rule IDs — behavior an agent could not get from readOnlyHint/openWorldHint alone. The one redundant line ('read-only and local') merely echoes annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, followed by the operational caveat and the return shape in a compact JSON sketch. The embedded structure listing is dense but justified given there is no output schema; a couple of ellipsis-truncated fields keep it slightly loose.

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?

With no output schema, the description supplies the response shape itself, and it covers the operational meaning, safety profile, and the fact that control lives in the console. Nothing needed to invoke or interpret this zero-parameter tool 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 no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. It correctly signals implicitly that this call needs no input.

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 and resource ('say whether the rules watcher is running and how many rules there are') and immediately defines what the 'watcher' is, so an agent can distinguish this status tool from rule CRUD siblings like list_rules or pause_rule.

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?

Gives clear context for when this is meaningful ('with it stopped no rule does anything') and an explicit exclusion ('There is no tool to start or stop the watcher'). It stops short of routing the agent to a sibling for rule-level detail (e.g. list_rules), so it is clear but not fully comparative.

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