Skip to main content
Glama

wait-seconds

Pause execution for a specified number of seconds during blockchain operations. Use this tool to manage timing in automated workflows or wait for transaction confirmations.

Instructions

Wait the given seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secondsYes

Implementation Reference

  • The execute function for the 'wait-seconds' tool, which waits for the specified number of seconds using the wait helper and returns a text response.
    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 parameter 'seconds' as a coerced number.
    parameters: z.object({
      seconds: z.coerce.number(),
    }),
  • The registerWaitSecondsTools function that adds the 'wait-seconds' tool to the FastMCP server using server.addTool, including name, description, schema, and handler.
    export function registerWaitSecondsTools(server: FastMCP): void {
      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`,
              },
            ],
          };
        },
      });
    };
  • Invocation of registerWaitSecondsTools(server) as part of the central registerTools function.
    registerWaitSecondsTools(server);
  • Utility function 'wait' that creates a Promise resolved after the specified timeout in milliseconds using 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Wait') but doesn't describe what happens during the wait (e.g., blocking behavior, async handling), error conditions, or performance implications like maximum allowed seconds. This leaves significant gaps for a tool that controls execution flow.

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, direct sentence that front-loads the core functionality. There is no wasted language or unnecessary elaboration, making it efficient and 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 role in controlling execution timing and the lack of annotations or output schema, the description is insufficient. It doesn't explain what 'Wait' entails operationally (e.g., whether it blocks other actions), return values, or error handling, which are critical for an agent to use it correctly in a workflow.

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 meaningful context for the single parameter by specifying it represents 'seconds' to wait, which clarifies the unit and purpose beyond the schema's generic 'number' type. With 0% schema description coverage and only one parameter, this adequately compensates, though it doesn't detail constraints like minimum/maximum values.

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 clearly states the tool's purpose with a specific verb ('Wait') and resource ('the given seconds'), making it immediately understandable. However, it doesn't differentiate from the sibling tool 'wait-for-transaction-receipt', which serves a similar waiting function but with different context and parameters.

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 like 'wait-for-transaction-receipt' or general timing operations. It lacks context about appropriate scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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/metamask-mcp'

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