Skip to main content
Glama
Sign In
ado-workflows-mcp

ado-workflows-mcp

by grimlor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_work_item

Create any type of work item in an Azure DevOps project with custom fields and optional parent linkage.

Instructions

Create a new work item of any type.

Args: project: Azure DevOps project name. work_item_type: Work item type (e.g. "Task", "Bug", "Product Backlog Item"). fields: Dict mapping field reference names to values. parent_id: Optional parent work item ID for hierarchy linking. working_directory: Optional path for ADO context resolution.

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": {
      "project": "<project>",
      "work_item_type": "<work_item_type>",
      "fields": "<fields>",
      "parent_id": "<parent_id>",
      "working_directory": "<working_directory>"
    },
    "name": "create_work_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes
work_item_typeYes
fieldsYes
parent_idYes
working_directoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'create' and mentions hierarchy linking via parent_id, but does not disclose permissions, validation behavior, side effects, or rate limits. This is insufficient for a mutation tool.

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?

The description is front-loaded with the main purpose, followed by a clean args list. It is concise and contains no redundant information, though the parameter explanations could be slightly more streamlined.

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?

Given no annotations and 5 parameters, the description covers the creation purpose and all parameters. Output schema exists, so return value details are not needed. It does not mention error scenarios or prerequisites, but is generally complete for agent use.

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?

With 0% schema description coverage, the description compensates by explaining all 5 parameters, including examples for work_item_type and clarifying parent_id's role and fields as a dictionary. However, it lacks constraints on which field names are valid or case sensitivity.

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 'Create a new work item of any type', using a specific verb and resource. It distinguishes itself from sibling tools like clone_work_item and update_work_item, which have different purposes.

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 usage for creating new items but does not explicitly state when to use this tool versus alternatives like clone_work_item (for copying) or update_work_item (for modifying). No when-not or alternative guidance is provided.

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