Skip to main content
Glama
danielealbano

mcp-for-azure-devops-boards

azdo_create_work_item

Creates new work items in Azure DevOps projects with customizable fields, types, and metadata for tracking tasks, bugs, and user stories.

Instructions

Create work item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoComma-separated tags
stateNoInitial state (New, Active, Resolved, etc.)
titleYesWork item title
effortNoEffort estimate in hours
fieldsNoOptional extra fields as JSON string (for custom fields)
formatNoFormat for large text fields (description, acceptance criteria, repro steps, justification): "markdown" or "html" (default: "markdown")markdown
projectYesAzDO project name
activityNoActivity type (Development, Testing, Documentation, etc.)
priorityNoPriority (1-4, where 1 is highest)
severityNoSeverity for bugs (Critical, High, Medium, Low)
area_pathNoArea path (e.g., "MyProject\\Team1")
board_rowNoBoard row/swimlane to place the work item in
parent_idNoID of parent work item
start_dateNoStart date (YYYY-MM-DD)
assigned_toNoUser to assign the work item to (email or display name)
descriptionNoWork item description (use markdown syntax when format is "markdown", HTML tags when format is "html")
repro_stepsNoReproduction steps (use markdown syntax when format is "markdown", HTML tags when format is "html")
target_dateNoTarget/due date (YYYY-MM-DD)
board_columnNoBoard column to place the work item in
organizationYesAzDO org name
story_pointsNoStory points for estimation
justificationNoJustification (CMMI process template; use markdown syntax when format is "markdown", HTML tags when format is "html")
iteration_pathNoIteration path (e.g., "MyProject\\Sprint 1"), use azdo_get_team_current_iteration to get the current iteration
remaining_workNoRemaining work in hours
work_item_typeYesType of work item (User Story, Epic, Feature, etc.)
acceptance_criteriaNoAcceptance criteria (use markdown syntax when format is "markdown", HTML tags when format is "html")
Behavior1/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It fails to mention that this tool creates a new work item in Azure DevOps, any potential side effects (e.g., notifications, state transitions), required permissions, or error conditions. Without this, the agent cannot anticipate the tool's impact.

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

Conciseness2/5

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

The description is extremely concise (three words) but at the expense of informativeness. It lacks structure and fails to front-load critical details. True conciseness would preserve meaning while reducing verbosity; here, meaning is sacrificed.

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

Completeness1/5

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

Given the high complexity (26 parameters, no output schema, no annotations), the description is wholly inadequate. It does not explain what happens upon creation (e.g., returns work item ID), error handling, or integration with sibling tools. The agent has no contextual understanding of the tool's role.

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 description coverage is 100%, so all 26 parameters have descriptive definitions in the input schema. The description 'Create work item' adds no extra semantic value beyond what is already documented in the schema. Baseline score is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create work item' is a tautology that merely restates the tool's name. It does not specify the type of work item, the Azure DevOps context, or any distinguishing features. The agent gains no additional understanding of the tool's unique purpose beyond the name itself.

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 provides no guidance on when to use this tool versus sibling tools such as azdo_update_work_item or azdo_query_work_items. It does not mention prerequisites, typical scenarios, or situations where this tool is preferred. Minimal context is implied from the name, but explicit guidance is absent.

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/danielealbano/mcp-for-azure-devops-boards'

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