Skip to main content
Glama
enesjakozh
Garoth

Sleep MCP Server

by Garoth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Servidor MCP de suspensión

Un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona una herramienta sencilla de suspensión/espera. Útil para añadir retrasos entre operaciones, como la espera entre llamadas a la API o para probar sistemas eventualmente consistentes.

Herramientas disponibles

  • sleep : esperar una duración especificada en milisegundos

Related MCP server: MCP-Wait

Instalación

git clone https://github.com/Garoth/sleep-mcp.git
npm install

Configuración

Agregue a su archivo de configuración de Cline MCP (p. ej. ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json):

{
  "mcpServers": {
    "sleep": {
      "command": "node",
      "args": ["/path/to/sleep-server/build/index.js"],
      "disabled": false,
      "autoApprove": [],
      "timeout": 300
    }
  }
}

Nota: El parámetro de timeout especifica el tiempo máximo (en milisegundos) que el servidor MCP esperará una respuesta antes de agotar el tiempo de espera. Esto es especialmente importante para la herramienta de suspensión, ya que establecer un tiempo de espera inferior a la duración de la suspensión provocará un fallo en la operación. Asegúrese de que el valor del tiempo de espera sea siempre mayor que la duración máxima de suspensión que planea utilizar.

Desarrollo

Configuración de pruebas

Las pruebas verifican la funcionalidad del sueño con diferentes duraciones:

npm test

Edificio

npm run build

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Available Tools

1 tool
sleepB

Wait for a specified duration

ParametersJSON Schema
NameRequiredDescriptionDefault
millisecondsYesDuration to wait in milliseconds

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions waiting but doesn't specify whether this is blocking, if it affects system resources, what happens during the wait, or any error conditions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise at just four words, front-loaded with the core function, and contains zero wasted information. Every word earns its place in communicating the essential purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter with full schema coverage, no output schema), the description is minimally adequate but lacks context about behavioral aspects like blocking nature or error handling. It's complete enough for basic understanding but misses deeper operational details.

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 schema description coverage is 100%, with the parameter 'milliseconds' fully documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline of 3 for high schema coverage.

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 'Wait for a specified duration' clearly states the tool's function with a specific verb ('Wait') and resource ('duration'), making the purpose immediately understandable. However, it doesn't differentiate from siblings since there are none, so it can't achieve a perfect 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage instructions or exclusions.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedsleep
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose is singular and clearly defined, eliminating any ambiguity.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other names to compare it against. The tool name 'sleep' is straightforward and follows a simple verb pattern, which is consistent in this minimal context.

Tool Count2/5

A single tool for a server named 'Sleep MCP Server' feels thin and under-scoped, as it only provides a basic waiting function without any related operations like scheduling, monitoring, or configuration. This minimal set may not fully represent a server's purpose beyond a trivial utility.

Completeness1/5

The server is severely incomplete for any meaningful domain beyond a simple delay function; there are no tools for related tasks such as setting alarms, managing sleep schedules, or handling interruptions. This single tool offers no coverage for a broader sleep-related workflow, leading to significant gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Wait Timer Server

    199-mcp
    A
    license
    A
    quality
    D
    maintenance
    Provides a simple 'wait' tool that introduces deliberate pauses into workflows executed by MCP clients, allowing time for asynchronous operations to complete before proceeding to the next step.
    1
    32 npm
    1
    MIT

  • MCP-Wait

    automation-ai-labs
    A
    license
    B
    quality
    D
    maintenance
    A simple MCP server that provides waiting functionality to pause until other tasks finish, with progress reporting and support for CLI or HTTP server with SSE.
    1
    23 npm
    5
    MIT

  • MCP REST API Server

    vinaykp
    F
    license
    Not graded
    quality
    D
    maintenance
    A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
    -

  • mcp-wait

    lzientek
    A
    license
    A
    quality
    D
    maintenance
    A minimal MCP server that lets AI agents pause for a specified duration before resuming their workflow. Useful for polling patterns like waiting for PR approval or file creation.
    1
    6 npm
    MIT