Skip to main content
Glama
ni-c

mcp-hub

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Wake a sleeping server

wake_server
Idempotent

Start an on-demand server now to reduce latency for its first tool call. No action if it is already running.

Instructions

Start an on-demand server now so its first tool call is fast. No-op if it is already running.

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.
toolCountYes

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"
+    },
+    "toolCount": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "name",
+    "status",
+    "toolCount"
+  ],
+  "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?

Description adds meaningful behavioral detail beyond annotations, including the no-op behavior and the side effect of waking a server. Annotations already cover idempotency and non-destructiveness, and the description is consistent with them.

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 short, focused sentences with no filler. The primary purpose is stated first, followed by the important no-op edge case.

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 one-parameter tool with an output schema, the description covers the essential context: when to invoke, the effect, and the idempotent behavior. No significant information is missing.

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?

The only parameter 'server' is fully documented in the schema as 'Server name from list_servers', providing 100% coverage. The description adds no additional parameter detail, so baseline 3 is appropriate.

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?

Clearly states the action ('Start an on-demand server'), the target ('server'), and the benefit ('so its first tool call is fast'). Also distinguishes behavior with the no-op condition and contrasts indirectly with sleep_server.

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?

Provides clear context for when to use the tool ('start now', 'first tool call fast') and includes the no-op condition. Does not explicitly name alternatives like sleep_server, but the intended usage is 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