Skip to main content
Glama

List agents

list_agents
Read-onlyIdempotent

Supported coding agents with the instructions file each reads, its skills directory and where project MCP config goes.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds value by disclosing the fields each returned entry carries, which annotations cannot. It does not resolve whether the list is a fixed catalog of supported agents or a scan of what is installed locally, which is the main behavioral ambiguity for a no-argument tool.

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 economical clause that front-loads the resource and then the per-entry fields. It is dense and free of filler, though the fragment form ('Supported coding agents with the instructions file each reads...') reads awkwardly and would be clearer as a complete sentence naming the return action.

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 parameters, no output schema, and rich annotations, the description carries the main remaining burden of explaining what comes back, and it does so by naming the three data points per agent. The only material gap is the static-catalog versus installed-agents distinction, which matters for how an agent interprets an empty or partial result.

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?

The tool takes zero parameters, so the baseline applies and there is nothing for the description to disambiguate at the argument level. No misleading parameter hints are present.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (supported coding agents) and enumerates what each entry contains: instructions file, skills directory, and project MCP config location. However, it is a noun phrase with no verb, so an agent must infer that the tool returns this catalog rather than configuring or validating it. It is distinguishable from siblings like get_loadout, but only by topic, not by an explicit statement of action.

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 when-to-use or when-not-to-use guidance, and no routing to alternatives such as get_install_instructions or get_loadout, which plausibly overlap with agent setup information. The agent is left to guess whether this is the right entry point for setup questions or only a static reference lookup.

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.