Skip to main content
Glama

List MCP servers

list_servers
Read-onlyIdempotent

Retrieve all available MCP servers and their status from the hub so you can see what is accessible before connecting or managing them.

Instructions

List all MCP servers available through this hub, with their status. Call this first to see what is available. Servers marked "hidden" serve their tools only via their own endpoint, but wake_server/sleep_server still manage them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
serversYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • addedOutput schema / properties / servers / items / properties / locked
      Added value: +{
      +  "description": "Present for a server with locked tools: whether they are locked for you right now.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / servers / items / properties / lockedTools
      Added value: +{
      +  "description": "The locked tools, as name patterns; absent when every tool is locked.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / servers / items / properties / unlockedUntil
      Added value: +{
      +  "description": "When your unlock ends, if you hold one (ISO 8601).",
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv0.11.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "servers": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "description": {
      +            "description": "The child's own title, empty if it has never connected.",
      +            "type": "string"
      +          },
      +          "hidden": {
      +            "const": true,
      +            "description": "Present only for a server whose tools are served by its own endpoint alone.",
      +            "type": "boolean"
      +          },
      +          "name": {
      +            "description": "Name to pass to the other tools.",
      +            "type": "string"
      +          },
      +          "status": {
      +            "description": "What the hub is currently doing with this server.",
      +            "enum": [
      +              "starting",
      +              "up",
      +              "down",
      +              "stopped",
      +              "sleeping",
      +              "unauthorized"
      +            ],
      +            "type": "string"
      +          },
      +          "toolCount": {
      +            "description": "Tools this server offers through the hub, after its filter.",
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "description",
      +          "status",
      +          "toolCount"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "servers"
      +  ],
      +  "type": "object"
      +}
  3. First observedv0.9.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already cover read safety and idempotence, so the description is not required to restate them. What it does add is genuinely non-obvious behavior: 'hidden' servers expose tools only through their own endpoint yet remain controllable via wake_server/sleep_server, which an agent could not infer from the schema or annotations.

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?

It uses three short sentences, each adding distinct information: what is listed, when to call it, and how to handle hidden entries. The operational instruction to call it first is front-loaded in the second sentence, with no filler or restatement of the name.

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 parameters, strong annotations, and an output schema handling the return shape, the description carries only the burden of discovery guidance and the hidden-server caveat, both of which are present. Nothing an agent needs before calling it is missing.

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 there is nothing for the description to disambiguate — the baseline for a parameterless tool applies. The note about hidden servers effectively clarifies what the returned entries can contain, which is a mild plus.

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 uses a specific verb and resource ('List all MCP servers') and adds scope detail ('with their status' and the meaning of a 'hidden' marking). It is distinguishable from list_tools by resource type, though it never names list_tools as the companion for enumerating tools, so the sibling distinction is inferred rather than stated.

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

Usage Guidelines4/5

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

It gives a clear directive to call this first when discovering what is available, which firmly establishes the entry-point usage. It stops short of stating when not to call it — for example, that agents who already know the server name should skip straight to list_tools or get_tool_schema.

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