Skip to main content
Glama
cexll
by cexll

timeout-test

Test timeout prevention by running for a specified duration in milliseconds. Use this tool to verify timeout handling mechanisms in code execution workflows.

Instructions

Test timeout prevention by running for a specified duration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationYesDuration in milliseconds (minimum 10ms)

Implementation Reference

  • The main handler function that executes the timeout test by sleeping for the specified duration in steps, reporting progress, and returning a summary of the execution.
    execute: async (args, onProgress) => {
      const duration = args.duration as number;
      const steps = Math.ceil(duration / 5000); // Progress every 5 seconds
      const stepDuration = duration / steps;
      const startTime = Date.now();
    
      const results: string[] = [];
      results.push(`Starting timeout test for ${duration}ms (${duration / 1000}s)`);
    
      for (let i = 1; i <= steps; i++) {
        await new Promise(resolve => setTimeout(resolve, stepDuration));
        const elapsed = Date.now() - startTime;
        results.push(`Step ${i}/${steps} completed - Elapsed: ${Math.round(elapsed / 1000)}s`);
      }
    
      const totalElapsed = Date.now() - startTime;
      results.push(`\nTimeout test completed successfully!`);
      results.push(`Target duration: ${duration}ms`);
      results.push(`Actual duration: ${totalElapsed}ms`);
    
      return results.join('\n');
    },
  • Zod schema defining the input parameter 'duration' as a number with minimum 10ms.
    const timeoutTestArgsSchema = z.object({
      duration: z.number().min(10).describe('Duration in milliseconds (minimum 10ms)'),
    });
  • Registration of the timeoutTestTool into the central toolRegistry along with other tools.
    toolRegistry.push(
      askCodexTool,
      batchCodexTool,
      // reviewCodexTool,
      pingTool,
      helpTool,
      versionTool,
      brainstormTool,
      fetchChunkTool,
      timeoutTestTool
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'runs for a specified duration' to test timeout prevention, implying it simulates a time-consuming operation. However, it lacks details on potential side effects (e.g., resource consumption), error handling, or what constitutes a successful test. For a tool with no annotations, this is a significant gap in behavioral context.

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, efficient sentence: 'Test timeout prevention by running for a specified duration.' It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple tool with one parameter. Every part of the sentence earns its place by conveying essential information.

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 complexity (simple with one parameter) and the absence of annotations and output schema, the description is incomplete. It explains what the tool does but lacks context on how it integrates with sibling tools, what the expected outcome is (e.g., success/failure indicators), or any behavioral nuances. For a testing tool, more guidance on interpretation would be helpful.

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 input schema has 100% description coverage, with the 'duration' parameter fully documented in the schema (type, minimum, description). The description adds no additional meaning beyond the schema, as it only mentions 'a specified duration' without elaborating on units or constraints. Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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: 'Test timeout prevention by running for a specified duration.' It specifies the verb ('Test timeout prevention') and resource/action ('running for a specified duration'), making it clear what the tool does. However, it doesn't explicitly distinguish itself from sibling tools like 'ping' or 'version', which might also test system functionality.

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. It doesn't mention any prerequisites, context, or exclusions, and there's no comparison to sibling tools like 'ping' (which might test connectivity) or 'ask-codex' (which might involve processing). This leaves the agent with minimal direction on appropriate usage scenarios.

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/cexll/codex-mcp-server'

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