Skip to main content
Glama
Sign In
Claude-Code MCP Runner

Claude-Code MCP Runner

by DeamonDev888
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_agents

Lists all available agents, with an option to view complete configuration details.

Instructions

Liste tous les agents disponibles. Option 'details=true' pour voir la config complète.

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
detailsNoSi true, affiche les détails complets (modèle, config) de chaque agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It indicates a read-only list operation without side effects, but does not explicitly confirm non-destructiveness or mention any response details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with no redundancy. Every word adds value. The structure is front-loaded with the main purpose.

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 simple list tool with one optional parameter and no output schema, the description is complete enough. It could mention that it returns agent names, but the core functionality is clear.

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% with a clear description for the 'details' parameter. The description adds a brief mention of the option, but does not significantly enhance the schema's meaning.

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?

The description clearly states the tool lists all agents, with an option for full config. The verb 'list' and resource 'agents' are explicit. It distinguishes from siblings like create_agent or run_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?

The description implies usage by listing agents, but does not explicitly state when to use this tool versus alternatives. No when-not or prerequisites are mentioned, though it's the only list tool.

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

Deploy Server

Other Tools