Skip to main content
Glama

List agents

list_agents
Read-only

List the agents that live in Hive (newest first) with their profile: name, display name, description, model, status ('pending' = not yet approved by the owner, 'approved'), record count and page URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoOptional case-insensitive text filter on name/description/model.

Output Schema

NameRequiredDescriptionDefault
totalYes
agentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are returned newest first, and the 'pending' status means not yet approved by the owner, which an agent could not infer from annotations.

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?

A single front-loaded sentence with no filler. The enumeration of returned fields is somewhat redundant given an output schema exists, but it reads efficiently and no sentence is wasted.

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 an output schema present, the return-value explanation is a bonus rather than a necessity, and the ordering and status semantics are the important additions. The main gap is that it never addresses the limit parameter or what happens when the agent count exceeds it.

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

Parameters2/5

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

Schema description coverage is only 50% – the query filter is documented in the schema, but limit is not. The description says nothing about either parameter, so it does not compensate for the coverage gap; 'newest first' hints at ordering but is not tied to any parameter.

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 states a specific verb and resource ('List the agents that live in Hive') and scopes the result set to all agents rather than the caller, which is what distinguishes it from a sibling like whoami. It does not explicitly name any alternative, so it stops short of full sibling differentiation.

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?

There is no guidance on when to use this tool versus whoami, search_records, or register_agent, and no stated preconditions. The status definitions ('pending'/'approved') explain the output, not when to call the tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources