Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

agents_list

Read-onlyIdempotent

List all AI agents configured in the workspace.

Returns agents with their basic info, trigger count, and knowledge collection count.

Each agent's description field tells you when that agent is useful. If you're a router-style agent deciding whether to delegate via agent.handoff, read descriptions and pick the best fit.

Use this to:

  • See all configured AI agents

  • Filter by status (active/paused/archived)

  • Get agent IDs for further operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by status ('active' / 'paused' / 'archived'). Omit for all.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Changed2 schema fields changed
    • removedInput schema / properties / enabled
      Removed value: -{
-  "description": "Filter by enabled status (true = enabled only, false = disabled only, omit = all)",
-  "type": "boolean"
-}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Filter by status ('active' / 'paused' / 'archived'). Omit for all.",
+  "enum": [
+    "active",
+    "paused",
+    "archived"
+  ],
+  "type": "string"
+}
  5. Changed2 schema fields changed
    • addedInput schema / properties / enabled
      Added value: +{
+  "description": "Filter by enabled status (true = enabled only, false = disabled only, omit = all)",
+  "type": "boolean"
+}
    • removedInput schema / properties / status
      Removed value: -{
-  "description": "Filter by status ('active' / 'paused' / 'archived'). Omit for all.",
-  "enum": [
-    "active",
-    "paused",
-    "archived"
-  ],
-  "type": "string"
-}
  6. Changed2 schema fields changed
    • removedInput schema / properties / enabled
      Removed value: -{
-  "description": "Filter by enabled status (true = enabled only, false = disabled only, omit = all)",
-  "type": "boolean"
-}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Filter by status ('active' / 'paused' / 'archived'). Omit for all.",
+  "enum": [
+    "active",
+    "paused",
+    "archived"
+  ],
+  "type": "string"
+}
  7. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety bar is satisfied. The description adds genuine behavioral value by disclosing the return shape (basic info, trigger count, knowledge collection count) and the semantic meaning of the per-agent description field, which the annotations cannot convey.

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 core action and return summary, then uses a short bullet list for the enumerated uses. Slightly padded by the router/handoff paragraph, but every part is relevant and no sentence is filler.

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 carries the return-shape burden and does so (basic info plus trigger and knowledge counts). It is complete enough to call correctly; only minor gaps remain, such as pagination or result size behavior.

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 both parameters—including the status enum and the workspace override—are already fully documented in the schema. The description restates the status filter ('active/paused/archived') but adds no syntax or semantics beyond it, so the baseline of 3 applies.

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?

States a specific verb and resource ('List all AI agents configured in the workspace'), immediately distinguishing it from single-agent siblings like agents_get. An agent can tell what this returns without opening the schema.

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?

Provides clear when-to-use context: see all agents, filter by status, and retrieve agent IDs for further operations. It also frames the router/delegation scenario, but names no explicit exclusion or alternative sibling (e.g., 'use agents_get for a single agent'), so it stops short of a full 5.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources