Skip to main content
Glama
Sign In
Coding Agent MCP Server

Coding Agent MCP Server

by Sukarth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delay

Pause execution for a defined number of milliseconds or seconds to control timing during automated workflows or sequences.

Instructions

Wait for a specified amount of time

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delay"
  }
}

Input Schema

NameRequiredDescriptionDefault
millisecondsNoTime to wait in milliseconds
secondsNoTime to wait in seconds (alternative to milliseconds)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

The description is minimal and does not disclose behavioral traits such as whether the delay blocks execution, precision limits, or if simultaneous calls are handled. With no annotations, the description carries full burden but fails to provide sufficient detail.

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 a single, concise sentence that immediately conveys the tool's purpose with no unnecessary words. It is appropriately front-loaded and efficient.

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 and the schema providing parameter details, the description is minimally adequate. However, it could be improved by noting behavior when both parameters are provided or specifying that the tool blocks execution.

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 coverage is 100% with clear descriptions for both parameters. The tool description adds no extra meaning beyond what the schema already provides, so it meets the baseline.

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 amount of time' clearly states the tool's action and resource (time delay). It is distinct from sibling tools which focus on file and command operations, so purpose is clear.

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?

No guidance is provided on when to use this tool versus alternatives. Although no similar tool exists among siblings, the description does not offer any context on typical use cases or prerequisites.

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