Skip to main content
Glama

List agent tasks

list_agent_tasks
Read-only

List the organisation's AI agents (the task definitions behind agent runs) with the fields that decide whether each one can work the AI board: whether it is enabled, whether it is designated as a board worker, its tool_profile and autonomy_level, its trigger kind, and whether its runs carry an identity that can write. Every agent gets a can_work_board verdict, and one that cannot carries cannot_work_board_reason naming the blocking condition. Use this to answer 'why is nothing on the board being worked': when agents_that_can_work_the_board is 0, every ticket filed in this organisation is escalated to a human instead of worked. Complements list_agent_runs, which shows dispatched runs but never the agents behind them. Read-only.

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_agent_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_workers_onlyNoOnly return agents already designated as board workers (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=true, and the description adds substantive behavior: the per-agent can_work_board verdict, the cannot_work_board_reason field naming the blocking condition, and the downstream effect that tickets are escalated to a human rather than worked. That is real operational context beyond the safety hint, and the "Read-only" statement is consistent with the annotation rather than contradicting it.

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?

The first sentence is front-loaded with the core purpose, and the diagnostic use case follows logically. It is dense — the opening sentence packs a long field enumeration — but each clause carries information an agent needs to interpret the verdict fields, so the length is mostly earned rather than padding.

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

Completeness5/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 full burden of explaining returns, and it does so: it names the verdict and reason fields and interprets the zero-agents case. For a one-parameter read-only list tool, nothing an agent needs in order to call it and interpret the result is missing.

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?

There is a single parameter and schema description coverage is 100%, so the schema already fully documents board_workers_only, including its default. The description hints at the concept by listing board-worker designation as a returned field, but adds no filtering semantics or default behavior of its own, so the baseline 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 the organisation's AI agents") and immediately clarifies the resource with a parenthetical ("the task definitions behind agent runs"). It also enumerates the decisive fields returned (enabled, board worker designation, tool_profile, autonomy_level, trigger kind, writable run identity), so an agent can tell exactly what it will get and how it differs from list_agent_runs.

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

Usage Guidelines5/5

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

Gives an explicit use case in the user's own idiom: "Use this to answer 'why is nothing on the board being worked'", and explains the consequence when agents_that_can_work_the_board is 0. It also names the alternative — list_agent_runs — and states the discriminating condition (runs vs. the agents behind them), which is exactly the when-vs-alternative guidance expected.

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.