Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Create work item

devops_work_item_create

Creates a new Azure DevOps work item of a specified type and sets its fields, with optional dry-run validation to check rules before saving.

Instructions

Create a new work item of the specified work item type.

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": {
      "type": "<type>",
      "fields": "<fields>"
    },
    "name": "devops_work_item_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe work item type to create, e.g. 'Task', 'Bug', 'User Story'.
fieldsYesList of field objects to set on the new work item. Each entry must have 'name' (field reference name, e.g. 'System.Title') and 'value'. An optional 'format' key accepts 'Html' or 'Markdown' (defaults to 'Html' when omitted; use 'Markdown' only if the project supports it).
validate_onlyNoIf True, validate the input against system rules without saving the work item (dry run).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond the operation—no permissions, side effects, validation behavior, or field requirements—and it does not contradict the 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?

A single front-loaded sentence with no filler or redundant wording. It is appropriately terse, though its brevity shifts most explanatory burden to the schema and annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema, annotations, and output schema cover much of what an agent needs, so the description need not explain return values. However, for a create mutation it omits project/team context, required-field expectations, and usage relative to update, leaving a meaningful gap.

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 100%, so parameter meanings are fully documented in the schema, including type examples and the validate_only dry-run behavior. The description only references the work item type at a high level and adds no syntax or constraints beyond what the schema already states.

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?

Uses a specific verb ('Create') and resource ('work item'), and notes that the work item type is caller-supplied. It does not distinguish this tool from siblings such as devops_work_item_update or devops_work_item_delete, so it is clear but not sibling-differentiating.

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?

Provides no when-to-use or when-not-to-use guidance, no prerequisites such as project/team context, and no mention of alternatives like update for existing items. The only usage signal is the create verb itself.

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