Skip to main content
Glama

wait-seconds

Introduces delays in blockchain interactions by pausing execution for a specified number of seconds, enabling controlled timing for transaction sequences and automated workflows.

Instructions

Wait the given seconds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secondsYes

Implementation Reference

  • The async execute function that implements the core logic of the wait-seconds tool by waiting the specified seconds using the wait helper and returning a text confirmation.
    execute: async (args) => {
      const seconds = args.seconds
      await wait(seconds * 1000)
      return {
        content: [
          {
            type: "text",
            text: `Wait for ${seconds} seconds`,
          },
        ],
      }
    },
  • Zod schema defining the input parameters for the tool, specifically 'seconds' coerced to number.
    parameters: z.object({
      seconds: z.coerce.number()
    }),
  • The registration of the 'wait-seconds' tool via server.addTool, including name, description, schema, and handler reference.
    server.addTool({
      name: "wait-seconds",
      description: "Wait the given seconds",
      parameters: z.object({
        seconds: z.coerce.number()
      }),
      execute: async (args) => {
        const seconds = args.seconds
        await wait(seconds * 1000)
        return {
          content: [
            {
              type: "text",
              text: `Wait for ${seconds} seconds`,
            },
          ],
        }
      },
    });
  • Helper function that performs the asynchronous wait using Promise and setTimeout.
    async function wait(timeout: number) {
      return new Promise((resolve) => {
        setTimeout(() => {
          resolve(undefined)
        }, timeout)
      })
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'wait' but doesn't disclose key behavioral traits such as whether it's blocking, if it affects other operations, error handling, or any side effects. This leaves the agent guessing about the tool's impact and safety.

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 with a single sentence, 'Wait the given seconds,' which is front-loaded and wastes no words. It efficiently conveys the core action without unnecessary details, making it easy to parse.

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

Completeness2/5

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

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what happens during the wait, return values, or potential errors. For a tool that could impact execution flow, more context is needed to ensure safe and correct usage.

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

Parameters4/5

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

The description adds minimal meaning beyond the input schema, which has 0% description coverage. It clarifies that 'seconds' is the parameter for waiting time, but doesn't specify units, valid ranges, or constraints. With only 1 parameter and no schema descriptions, the baseline is high, but it could be more informative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Wait the given seconds' states a clear action (wait) with a resource (seconds), but it's somewhat vague about what 'wait' means in this context—whether it's a blocking delay, a timer, or something else. It distinguishes from siblings like 'wait-for-transaction-receipt' by focusing on time-based waiting, but lacks specificity on the exact behavior.

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. For example, it doesn't mention if this is for general delays, testing, or synchronization, nor does it compare to siblings like 'wait-for-transaction-receipt' for blockchain-specific waits. The description alone offers no context for usage decisions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Xiawpohr/mcpilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server