Skip to main content
Glama

monitor_agents

Monitor agent status, activity, or communication in real time. Specify an agent, orchestration, room, or repository to receive updates at a chosen interval with customizable detail levels.

Instructions

Monitor agents with real-time updates using EventBus system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdNoOptional specific agent ID to monitor. If provided, will focus monitoring on this single agent. If not provided, will monitor all agents in the scope.
orchestrationIdNoOptional orchestration ID to monitor. If provided, will monitor all agents and tasks within this orchestration context.
roomNameNoOptional room name to monitor. If provided, will monitor communication and activity within this specific room.
repositoryPathNoOptional repository path to monitor. If provided, will monitor all agents and activities within this repository context. If not provided, uses current working directory.
monitoringModeNoType of monitoring to perform. "status" monitors agent status changes, "activity" monitors task and work activity, "communication" monitors room messages and coordination, "full" monitors all aspects.status
updateIntervalNoInterval in milliseconds between monitoring updates. Defaults to 2000ms (2 seconds). Lower values provide more frequent updates but use more resources.
maxDurationNoMaximum duration in milliseconds to monitor. Defaults to 50000ms (50 seconds). After this time, monitoring will automatically stop.
detailLevelNoLevel of detail in monitoring output. "summary" provides basic updates, "detailed" includes more context and metadata, "verbose" provides comprehensive information about all events.summary
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'real-time updates' and 'EventBus' but does not disclose resource consumption, potential side effects, or automatic stopping behavior (implied by maxDuration in schema). The lack of detail on what happens during and after monitoring reduces transparency.

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 description is a single sentence, making it brief and front-loaded. However, it is under-informative for a tool with 8 parameters and no other documentation. It earns its place but fails to deliver necessary detail, sacrificing substance for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema or annotations, the description is insufficient. It does not explain what the monitoring output looks like, how to stop monitoring, or how parameters like monitoringMode and detailLevel affect results. The tool is reasonably complex, but the description leaves significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description repeats only the term 'real-time updates' and adds no meaningful explanation of parameters beyond what the schema provides. It does not summarize parameter interplay or usage patterns, offering minimal added value.

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 clearly states the tool monitors agents with real-time updates via EventBus. The verb 'monitor' and the context of agents are specific, but it lacks differentiation from sibling tools like 'list_agents' which also involve agent observation. The schema provides additional detail via enums, but the description itself is somewhat generic.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'list_agents' for snapshots or 'broadcast_message_to_agents' for communication. There are no prerequisites or scenarios mentioned, leaving the agent to infer usage context.

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/ZachHandley/ZMCPTools'

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