Skip to main content
Glama
ni-c

mcp-hub

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List MCP servers

list_servers
Read-onlyIdempotent

List all available MCP servers and their status through this hub. Identify hidden servers that require direct endpoints while still managed by the hub.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
serversYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.9.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the main behavioral traits. The description adds context about hidden servers and their relationship with wake/sleep, which goes beyond the annotations without contradicting them. It does not introduce new behavioral details but reinforces the non-destructive nature implicitly.

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?

The description is three sentences, each serving a distinct purpose: stating the function, giving a usage directive, and explaining hidden-server behavior. It is front-loaded with the primary purpose and contains no redundant or extraneous information.

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?

Given the tool's simplicity (no parameters, clear annotations, output schema present), the description fully covers what an agent needs: what the tool does, when to call it, and a notable nuance about hidden servers. The presence of an output schema means the return value does not need to be described in the text.

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 has zero parameters, and the schema correctly reflects this (100% coverage with no fields to describe). Per the rubric, the baseline for 0 params is 4, and the description adds no unnecessary parameter details. The description's focus on server status and hidden behavior complements the empty parameter list.

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's purpose: 'List all MCP servers available through this hub, with their status.' It also includes a directive to call this first, which clarifies its role compared to sibling tools like list_tools. The additional note about hidden servers adds specificity without ambiguity.

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?

The description provides explicit usage guidance with 'Call this first to see what is available.' While it doesn't explicitly contrast with each sibling tool, the context makes it clear that this is the initial discovery step. The mention of hidden servers and wake_server/sleep_server hints at when further actions might be needed, fulfilling the requirement adequately.

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