Skip to main content
Glama

testmo_create_automation_run_thread

Create a thread in an automation run to enable parallel test execution lanes for submitting test results.

Instructions

Create a new thread in an automation run for submitting test results.

Threads represent parallel test execution lanes. After creating, use testmo_append_automation_run_thread to submit test results.

Args: automation_run_id: The automation run ID. elapsed_observed: Observed execution time in microseconds. elapsed_computed: Computed execution time in microseconds. artifacts: External test artifacts for the thread. fields: Custom fields for the thread.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
automation_run_idYes
elapsed_observedNo
elapsed_computedNo
artifactsNo
fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler function that creates a new thread in an automation run. Builds a request body with optional elapsed_observed, elapsed_computed, artifacts, and fields, then sends a POST request to /automation/runs/{automation_run_id}/threads.
    @mcp.tool()
    async def testmo_create_automation_run_thread(
        automation_run_id: int,
        elapsed_observed: int | None = None,
        elapsed_computed: int | None = None,
        artifacts: list[dict[str, Any]] | None = None,
        fields: list[dict[str, Any]] | None = None,
    ) -> dict[str, Any]:
        """Create a new thread in an automation run for submitting test results.
    
        Threads represent parallel test execution lanes. After creating, use
        testmo_append_automation_run_thread to submit test results.
    
        Args:
            automation_run_id: The automation run ID.
            elapsed_observed: Observed execution time in microseconds.
            elapsed_computed: Computed execution time in microseconds.
            artifacts: External test artifacts for the thread.
            fields: Custom fields for the thread.
        """
        data: dict[str, Any] = {}
        if elapsed_observed is not None:
            data["elapsed_observed"] = elapsed_observed
        if elapsed_computed is not None:
            data["elapsed_computed"] = elapsed_computed
        if artifacts:
            data["artifacts"] = artifacts
        if fields:
            data["fields"] = fields
        return await _request(
            "POST",
            f"/automation/runs/{automation_run_id}/threads",
            data=data if data else None,
        )
  • Registers testmo_create_automation_run_thread as an MCP tool on the FastMCP instance. The @mcp.tool() decorator from testmo/server.py (line 6: mcp = FastMCP('testmo-mcp')) registers this handler.
    @mcp.tool()
  • Docstring describing the function: creates a thread in an automation run for parallel test execution, referencing testmo_append_automation_run_thread for submitting results.
    """Create a new thread in an automation run for submitting test results.
    
    Threads represent parallel test execution lanes. After creating, use
    testmo_append_automation_run_thread to submit test results.
    
    Args:
        automation_run_id: The automation run ID.
        elapsed_observed: Observed execution time in microseconds.
        elapsed_computed: Computed execution time in microseconds.
        artifacts: External test artifacts for the thread.
        fields: Custom fields for the thread.
    """
  • Type-annotated parameter definitions serve as the input schema for the tool, with optional elapsed, artifacts, and fields parameters.
    automation_run_id: int,
    elapsed_observed: int | None = None,
    elapsed_computed: int | None = None,
    artifacts: list[dict[str, Any]] | None = None,
    fields: list[dict[str, Any]] | None = None,
Behavior2/5

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

No annotations provided, so description carries full burden. It only states creation and next step, but lacks details on side effects, permissions, or idempotency. Schema and description miss behavioral traits beyond basic operation.

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?

Concise: one sentence for purpose, one for context, then structured Args. No verbose or redundant text. Front-loaded key info.

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

Completeness4/5

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

Output schema exists, so return values not needed. Covers purpose, workflow, and parameters. Missing prerequisites (run must exist and be in progress) but overall adequate for a creation tool.

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?

Schema coverage is 0%, but description adds meaning: specifies units (microseconds) for elapsed fields, explains artifacts and fields as external/custom. However, no further details on format or constraints.

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

Purpose5/5

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

Clearly states 'Create a new thread in an automation run' and explains threads represent parallel test execution lanes. Differentiates from sibling tools like testmo_create_automation_run and testmo_append_automation_run_thread by describing the next step.

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

Usage Guidelines4/5

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

Explicitly tells when to use: after creating, use testmo_append_automation_run_thread to submit results. Provides context on parallel lanes, but doesn't mention prerequisites like an existing run.

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/strelec00/testmo-mcp'

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