mcp-for-azure-devops-boards

by danielealbano

Overview Schema Source Related Servers Discussions Admin

Rust

azdo_get_work_items

Retrieve multiple Azure DevOps work items by their IDs, optionally including the latest comments.

Instructions

Get multiple work items by IDs

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": {
      "organization": "<organization>",
      "project": "<project>",
      "ids": "<ids>"
    },
    "name": "azdo_get_work_items"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Work item IDs (comma-separated or array)
`project`	Yes	AzDO project name
`organization`	Yes	AzDO org name
`include_latest_n_comments`	No	Include the latest N comments (optional). Set to -1 for all comments.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 13, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / include_latest_n_comments / nullable
```
Removed value: -true
```

changedInput schema / properties / include_latest_n_comments / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

removedInput schema / title
```
Removed value: -"GetWorkItemsArgs"
```

Addedv1.0.0Jan 3, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the basic action with no mention of return format, authentication, rate limits, or side effects. For a read operation, it lacks depth.

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 a single sentence that is concise and front-loaded with action and resource. It is not verbose, but readability is adequate. Slightly reduced score because it omits details that would enhance understanding.

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?

Given low complexity (4 parameters, no output schema), the description is somewhat complete for a simple retrieval tool. However, it does not specify the return type or any limits, which would help an agent understand the outcome.

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?

Input schema covers all 4 parameters with descriptions. The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies per guidelines.

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?

Description clearly states the tool retrieves multiple work items by IDs. The verb 'Get' and resource 'work items' are specific. It distinguishes from sibling tool 'azdo_get_work_item' by indicating it handles multiple IDs, not a single one.

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 does not provide explicit guidance on when to use this tool versus alternatives like 'azdo_query_work_items' or 'azdo_get_work_item'. It is implied for batch retrieval by known IDs, but no when-not scenarios or prerequisites are mentioned.

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