Autopo

List agents

list_agents

Read-onlyIdempotent

The team: every agent with its role, title, state and whether it is on. Chat with one through ask_agent.

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

Name	Required	Description	Default
`company`	No	the company id (list_companies); not needed when you have one company, asked for otherwise

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 2, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / company / description

Previous value: -"the company id (list_companies); optional when you have one"New value: +"the company id (list_companies); not needed when you have one company, asked for otherwise"

removedInput schema / required
```
Removed value: -[]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the shape of the result (role, title, state, on/off), which is mild value given an output schema exists, and says nothing about scoping, ordering, or volume of agents returned.

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?

Two short sentences with no filler; the resource and its returned fields are front-loaded and the sibling pointer comes second. Slightly clipped phrasing ('whether it is on') costs a little precision but nothing 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?

For a single-parameter, read-only list tool with an output schema and full annotation coverage, the description supplies enough for correct invocation. The only gap is that the optional company scoping lives entirely in the schema rather than being reinforced in prose.

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 coverage is 100% and the single 'company' parameter is fully documented in the schema, including its conditional requirement. The description does not mention the company scoping at all, so it adds nothing beyond the schema — baseline 3 applies.

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 names the resource (every agent) and enumerates the returned attributes (role, title, state, on/off), which tells an agent exactly what this call yields. The verb is implicit rather than stated ('The team: every agent...'), but the listing semantics are unmistakable and it is clearly distinct from ask_agent.

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

Usage Guidelines3/5

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

It routes the agent to ask_agent for the adjacent action of chatting with an agent, which is useful context. However, it never says when to call this versus other roster/identity siblings such as whoami, company_overview, or list_companies, so usage is implied rather than specified.

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

All Autopo tools Inspect

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

Need Help?