Skip to main content
Glama
agenticmail

AgenticMail

Official

check_activity

Check which email agents are currently active and see if they have started processing your mail. Audit live multi-agent state including run duration, recent tools, and staleness.

Instructions

Check which agents are currently being woken by the dispatcher. Use this when you sent mail to a teammate and want to know if they have actually started working, or to audit the live multi-agent state. Returns active workers with the agent name, what triggered the wake (mail UID + subject, or task id), how long they have been running, the most recent tool they invoked, how many tool calls they have made, a stale flag (true if the dispatcher has not heartbeated in 90s+), and a preview of recently-finished work. Workers may run for hours — there is no auto-eviction; staleness is just a hint. Requires master key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoFilter to a specific agent by name (case-insensitive). Omit to see every active and recently-finished worker.
includeRecentNoInclude workers that finished in the last ~2 minutes (default: true). Set false to see only currently-running workers.
_accountNoOptional. Override identity for THIS call: pass the AgenticMail agent name (e.g. "Fola") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses return fields, staleness behavior (90s+), no auto-eviction, and master key requirement. Sufficiently transparent.

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?

Four sentences, front-loaded purpose, minimal redundancy. Could slightly tighten, but overall efficient and well-structured.

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?

No output schema, but description fully explains return fields, staleness, and behavior. Covers all necessary context for using the tool.

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 coverage is 100%, but description adds value: case-insensitive filtering for agent, meaning of stale flag, and details for _account authentication. Adds meaning beyond schema.

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 clearly states the tool checks which agents are being woken by the dispatcher, with specific use cases (after sending mail or auditing multi-agent state). It distinguishes from siblings like check_messages or check_tasks by focusing on agent activity.

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?

Explicit when to use: when you sent mail to a teammate to see if they started working, or to audit live multi-agent state. Does not mention when not to use or alternatives, but implied context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agenticmail/agenticmail'

If you have feedback or need assistance with the MCP directory API, please join our Discord server