Skip to main content
Glama
test-task-server

test-task-server

by shazamlll

Submit a test task

submit_test_task

Queues a test task for execution and returns a task ID for polling results. Optionally forces a deterministic pass/fail outcome for demos.

Instructions

Queue a test task for execution. Returns a task id; poll get_task_result for the outcome. Optional params.expectedOutcome ('passed' | 'failed') forces a deterministic outcome, useful for demos.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "target": "<target>"
    },
    "name": "submit_test_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable task name, e.g. 'smoke-login'
paramsNoOptional task parameters, e.g. { browser: 'chromium', expectedOutcome: 'failed' }
targetYesWhat the task runs against, e.g. 'staging-web'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/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. It does disclose non-obvious behavior — asynchronous execution, a returned task id, and that params.expectedOutcome can force a deterministic result — which is genuinely useful. However, it says nothing about whether the task really executes against the target, what side effects occur, or what permissions are needed.

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?

Three short sentences, front-loaded with the action, followed by the return/next-step contract and then the optional override. Nothing is padded or restated.

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 three-parameter submission tool with no output schema and no annotations, the description supplies the key missing pieces: the return value (task id) and the follow-up tool. It leaves the meaning of the 'target' parameter and the real-versus-mocked execution model implicit, which are the only notable gaps.

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 description coverage is already 100%, so the baseline is 3, but the description earns extra credit by explaining the semantics of params.expectedOutcome ('passed' | 'failed' forces a deterministic outcome, useful for demos) rather than merely restating the schema's example object.

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?

States a specific verb and resource ('Queue a test task for execution') and immediately differentiates itself from the sibling get_task_result by declaring it returns a task id that must be polled there for the outcome. An agent can place this tool in the workflow without opening any schema.

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?

Describes the intended flow explicitly: submit, then poll get_task_result. It also flags a special use case (forced deterministic outcome for demos). It stops short of stating when not to use it or how it relates to list_test_tasks, but the async workflow context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools