Skip to main content
Glama
Sign In
MDAN

MDAN

by khalilbenaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mdan_list_agents

Read-only

List all installed agents and their assigned roles to quickly assess the MDAN agent network and understand available capabilities.

Instructions

List all installed MDAN agents with their roles

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": "mdan_list_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds the scope ('all installed') and return content ('with their roles'), which is useful but minimal. No contradictions found.

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?

A single front-loaded sentence with zero waste. Every word contributes: the action, the resource, the scope, and the output content.

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?

The tool is simple — no parameters, read-only annotation, clear purpose. The absence of an output schema means the return structure is not fully specified, but the description does state that agents and their roles are returned, which is adequate for a low-complexity listing tool.

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?

There are zero parameters, so the description bears no obligation to explain parameter semantics. The schema coverage is trivially 100%, and the description's mention of what gets returned is enough context for a parameterless tool.

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 states a specific verb ('List'), resource ('all installed MDAN agents'), and scope ('with their roles'). It is distinguishable from sibling mdan_list_workflows by the resource type, though it does not explicitly name sibling alternatives.

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?

Usage is implied through the clear purpose — if you need to enumerate installed agents and their roles, this is the tool. No explicit when/when-not guidance or alternatives are named, but for a simple read-only list tool the context is reasonably inferable.

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