Skip to main content
Glama
strelec00

testmo-mcp

by strelec00
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

testmo_complete_automation_run

Complete an automation run in Testmo by providing its ID. Optionally auto-set execution time from creation to completion.

Instructions

Mark an automation run as completed.

Args: automation_run_id: The automation run ID to complete. measure_elapsed: Auto-set execution time from creation to completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
automation_run_idYes
measure_elapsedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • testmo/tools/automation.py:204-222 (handler)
    Handler function that marks an automation run as completed. Accepts automation_run_id and optional measure_elapsed bool. Sends a POST request to /automation/runs/{automation_run_id}/complete.
    @mcp.tool()
async def testmo_complete_automation_run(
    automation_run_id: int,
    measure_elapsed: bool | None = None,
) -> dict[str, Any]:
    """Mark an automation run as completed.

    Args:
        automation_run_id: The automation run ID to complete.
        measure_elapsed: Auto-set execution time from creation to completion.
    """
    data: dict[str, Any] = {}
    if measure_elapsed is not None:
        data["measure_elapsed"] = measure_elapsed
    return await _request(
        "POST",
        f"/automation/runs/{automation_run_id}/complete",
        data=data if data else None,
    )
  • testmo/tools/automation.py:204-204 (registration)
    Registered as a tool via @mcp.tool() decorator from FastMCP (testmo/server.py).
    @mcp.tool()
  • testmo/tools/automation.py:205-208 (schema)
    Input schema: automation_run_id (int, required), measure_elapsed (bool, optional). Returns dict[str, Any].
    async def testmo_complete_automation_run(
    automation_run_id: int,
    measure_elapsed: bool | None = None,
) -> dict[str, Any]:

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It explains the measure_elapsed parameter's effect (auto-set time) but doesn't disclose error behavior, idempotency, or the response format. The output schema exists but is not described.

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: one front-loaded sentence and a list of args. Every sentence serves a purpose with no fluff, making it easy for the agent to parse quickly.

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?

For a simple two-parameter tool with an output schema, the description covers the main purpose and explains one parameter's behavior. It lacks detail on error conditions or prerequisites (e.g., run must be in progress), but is largely complete for the action described.

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 0%, so description must add meaning. It explains automation_run_id as 'the ID to complete' and measure_elapsed as 'auto-set execution time'. While automation_run_id's description is merely a restatement, measure_elapsed benefits from the extra context. Overall adds value but could be more detailed.

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?

The description clearly states the verb 'mark' and resource 'automation run as completed', distinguishing it from sibling tools like testmo_create_automation_run and testmo_complete_automation_run_thread which operate on different stages or resources.

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

Usage Guidelines3/5

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

The description implies the tool is used to complete an automation run, but does not specify when not to use it or compare to alternatives. No prerequisites or context about run state are mentioned, leaving the agent to infer when this is appropriate.

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