Skip to main content
Glama
ni-c

mcp-hub

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List tools of a server

list_tools
Read-onlyIdempotent

Lists available tools for a specified MCP server, enabling discovery and inspection of tool schemas before invocation.

Instructions

List the tools of one MCP server with one-line descriptions. Use get_tool_schema before calling a tool for the first time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name from list_servers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolsYes
serverYes

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": {
+    "server": {
+      "type": "string"
+    },
+    "tools": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "annotations": {
+            "additionalProperties": true,
+            "description": "The child's own annotations, verbatim; absent if it declared none.",
+            "properties": {},
+            "type": "object"
+          },
+          "description": {
+            "description": "First line only, capped at 120 characters.",
+            "type": "string"
+          },
+          "hasOutputSchema": {
+            "const": true,
+            "description": "Present when the tool declares an output schema, which get_tool_schema returns.",
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "server",
+    "tools"
+  ],
+  "type": "object"
+}
  2. First observedv0.9.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint false. The description adds value by scoping the operation to one server and disclosing the output level ('one-line descriptions'), which is behavioral context beyond the 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?

Two compact sentences, each carrying useful information: what the tool lists and a clear follow-up workflow. No filler or redundancy.

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?

For a simple single-parameter read-only list tool with an output schema and safety annotations, the description plus schema provides everything an agent needs to call it correctly. Workflow guidance to get_tool_schema before first use is a valuable addition.

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 description coverage is 100%, so the 'server' parameter is already documented as a server name from list_servers. The description's 'one MCP server' phrasing reinforces that the parameter selects one server but adds little semantic detail beyond the schema.

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?

Description states a specific verb and resource: list the tools of one MCP server, and clarifies the output ('one-line descriptions'). It distinguishes the tool from siblings like list_servers and get_tool_schema without needing to inspect their schemas.

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 makes clear this is for listing a single server's tools and advises using get_tool_schema before first-time tool calls, which gives useful workflow context. It does not explicitly spell out when NOT to use it, but the sibling set makes that 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