Skip to main content
Glama
ivanostanin

Lucius

by ivanostanin
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

Rerun Test Results Manually

rerun_test_results_manually

Schedule manual reruns for selected failed test results by providing a launch ID and result IDs, with optional assignees and project override.

Instructions

Schedule manual reruns for selected launch results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneesNoOptional usernames to assign during manual rerun scheduling.
launch_idYesLaunch ID containing the failed results (required).
project_idNoOptional override for the default Project ID.
result_idsYesOne or more launch result IDs to schedule for manual rerun.
force_manualNoForce manual rerun mode when the upstream API supports it.
output_formatNoOutput format: 'json' (default) or 'plain'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneesNo
launch_idNo
result_idsNo
force_manualNo
scheduled_countNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.14.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "assignees": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Assignees"
+    },
+    "force_manual": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Force Manual"
+    },
+    "launch_id": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Launch Id"
+    },
+    "result_ids": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "integer"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Result Ids"
+    },
+    "scheduled_count": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Scheduled Count"
+    }
+  },
+  "title": "RerunTestResultsManuallyOutput",
+  "type": "object"
+}
  2. First observedv0.11.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations indicate mutation (readOnlyHint=false) but description adds no further behavioral context (e.g., async, side effects). Adequate given annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single, concise sentence. However, it might be too brief for a tool with 6 parameters; could include slightly more context without bloat.

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?

Does not explain what 'scheduling manual reruns' entails (e.g., triggers immediate execution or queues, impact on existing results). An output schema exists but description doesn't leverage context.

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?

All parameters have descriptions in the schema (100% coverage). The description adds no extra value beyond what schema provides.

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?

Description clearly states it schedules manual reruns for launch results. It distinguishes from sibling tools like submit_manual_test_results by the 'rerun' focus, but lacks explicit differentiation.

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 on when to use this tool versus alternatives like submit_manual_test_results or upload_test_results. Missing context on prerequisites or conditions.

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/ivanostanin/lucius-mcp'

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