Skip to main content
Glama
cmgmyr

hive

by cmgmyr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agent_list

Idempotent

Lists this project's agents with live status, optionally including closed or parked ones newest first, with paging support for large results.

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/5.0
Behavior4/5

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

Annotations declare idempotentHint=true and destructiveHint=false, so safety is partly covered; the description adds real behavioral detail the annotations don't — result ordering (newest first), the limit bound (default 20, max 100) and the cursor-based paging via next_before_id/before_id. It does not explain why readOnlyHint=false on what reads as a list operation, which is the one unexplained behavioral gap.

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?

Front-loads the purpose, then layers the include_closed variants and paging in one dense but well-ordered passage. Every clause earns its place; it is slightly compressed but not padded.

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?

With no output schema, the description compensates by describing the receipts and the next_before_id cursor, so an agent knows how to page and what ordering to expect. Combined with tested conditional behavior for include_closed and limit, it is nearly sufficient 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 the description reinforces the include_closed conditional, the limit default/max, and — beyond the schema — the pagination contract of feeding the receipt's next_before_id back as before_id. The only parameter not touched in prose is project_id, which the schema documents fully.

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?

States a specific verb and resource ("List this project's agents") plus scope ("with live status" and "this project's"), which cleanly separates it from single-agent tools like agent_status. It never names a sibling explicitly, so differentiation must be inferred from the scope phrasing rather than stated.

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 concrete when-to-use guidance for include_closed ("Without include_closed, this is every running agent... With include_closed, it is every agent") and an explicit when-not for project_id ("Use ONLY when the user explicitly asks for another project by name; otherwise stay in the current scope"). It stops short of routing the agent to alternatives such as agent_status or wake_list.

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