ado-mcp

ado_create_test_run

Create a test run for a test plan, optionally specifying test points to include.

Instructions

Create a test run for a plan (optionally over specific test points).

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>",
      "planId": "<planId>"
    },
    "name": "ado_create_test_run"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Test run name
`planId`	Yes	Test plan ID
`project`	No	Project name or ID (defaults to ADO_DEFAULT_PROJECT)
`pointIds`	No	Test point IDs to include
`automated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations are empty, so the description bears full responsibility for behavioral disclosure. It only states creation without mentioning side effects, permissions, or idempotency. Important traits like whether a run is automatically started or if it modifies existing data are omitted.

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, concise sentence that front-loads the core purpose. No extraneous words or repetition.

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?

For a create operation with five parameters, no output schema, and no annotations, the description is too minimal. It omits return value format, error conditions, and prerequisites (e.g., required permissions or existing plan). This leaves the agent underinformed.

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 high (80%), so the baseline is 3. The description adds context for 'planId' and 'pointIds' by mentioning 'for a plan (optionally over specific test points)', but does not enhance understanding of other parameters like 'automated' or 'project' beyond what schema provides.

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 action (create), the resource (test run), and the scope (for a plan, optionally over specific test points). This is specific and distinguishes it from sibling tools like 'ado_get_test_run' and 'ado_list_test_plans'.

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 implies usage when creating a test run but provides no explicit guidance on when not to use or alternatives. With many test-related siblings, such as 'ado_get_test_results' or 'ado_list_test_runs', the tool lacks clear decision criteria.

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

Deploy Server