Skip to main content
Glama
ni-c

mcp-hub

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Put a server to sleep

sleep_server
Idempotent

Stop an on-demand server immediately to avoid idle wait time, with automatic restart on the next tool call.

Instructions

Stop an on-demand server immediately instead of waiting for its idle timeout. It restarts automatically on the next tool call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name from list_servers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
statusYesWhat the hub is currently doing with this server.

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": {
+    "name": {
+      "type": "string"
+    },
+    "status": {
+      "description": "What the hub is currently doing with this server.",
+      "enum": [
+        "starting",
+        "up",
+        "down",
+        "stopped",
+        "sleeping",
+        "unauthorized"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "status"
+  ],
+  "type": "object"
+}
  2. First observedv0.9.0

TDQS

A4.8/5.0
Behavior5/5

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

The description adds behavioral details beyond the annotations: it explains the immediate stop, the automatic restart on next call, and implies non-destructive behavior. This supplements the idempotentHint and readOnlyHint 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?

The description is concise, two sentences, front-loaded with the action and key effect, with no unnecessary fluff.

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 that an output schema exists, the description does not need to explain return values. It provides sufficient context for the tool's purpose, parameter, and behavioral implications.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter 'server' is described with 'Server name from list_servers', which fully explains its meaning and source, covering 100% of 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?

The description clearly states the action ('Stop an on-demand server immediately') and its effect ('restarts automatically on the next tool call'), making the tool's purpose unambiguous.

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 usage guidance by contrasting with the idle timeout and mentioning automatic restart, but it does not explicitly compare with the sibling wake_server tool. Still, the core when-to-use context is present.

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