Skip to main content
Glama
cmgmyr

hive

by cmgmyr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agent_list

List all running agents in a project with live status. Optionally include closed or parked agents, with pagination for large histories.

Instructions

List this project's agents with live status. Without include_closed, this is every running agent, in full. With include_closed, it is every agent (running and closed/parked), newest first, bounded by limit (default 20, max 100); when the receipt carries next_before_id, page through the rest by passing it back as before_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows to return when include_closed is true, newest first. Default 20, max 100. Ignored otherwise.
before_idNoPage cursor for include_closed: only rows with id below this value. Pass the previous receipt's next_before_id to get the next page.
project_idNoDifferent project override. Use ONLY when the user explicitly asks for another project by name; otherwise stay in the current scope, even when results are empty.
include_closedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / before_id
      Added value: +{
+  "description": "Page cursor for include_closed: only rows with id below this value. Pass the previous receipt's next_before_id to get the next page.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max rows to return when include_closed is true, newest first. Default 20, max 100. Ignored otherwise.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses inclusion semantics (running vs closed/parked), ordering (newest first for include_closed), limit bounds, and pagination via next_before_id/before_id. It does not describe response fields or the sort order for the running-only mode, but the core behavior is well covered.

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?

The description is compact and front-loaded with purpose. Each clause adds meaningful detail about modes, defaults, bounds, or pagination, with no filler or repetition of schema content.

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

Completeness4/5

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

For a list tool with no output schema, it explains scope, filtering, ordering, limits, and pagination clearly. The main missing piece is what fields each agent row contains, though 'with live status' gives a reasonable expectation. Overall, it is complete enough for correct invocation.

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 75% and already documents limit, before_id, and project_id. The description adds relational semantics: include_closed toggles which agents are included, limit applies only in that mode, and before_id acts as the pagination cursor. This goes beyond merely repeating the 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 opens with a specific verb and resource: 'List this project's agents with live status.' This clearly identifies the operation and scope, and it is distinct from sibling tools like agent_status (single-agent status) or agent_close (mutation).

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 clearly explains the two modes (without include_closed vs with include_closed) and when to use before_id for pagination. However, it does not explicitly name an alternative tool or state when not to use agent_list, so it stops short of full exclusion guidance.

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

Deploy Server

Other Tools