Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Query work items (WIQL)

devops_work_item_query_by_wiql
Read-only

Run a WIQL query to retrieve matching Azure DevOps work items with selected fields, filters, ordering, and an optional result limit for focused reporting and triage.

Instructions

Execute a WIQL (Work Item Query Language) query and return the matching work items.

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": {
      "query": "<query>"
    },
    "name": "devops_work_item_query_by_wiql"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of results to return. Omit to use the server default.
queryYesThe WIQL query string. Example: "SELECT [System.Id], [System.Title], [System.State] FROM WorkItems WHERE [System.WorkItemType] = 'Bug' AND [System.State] <> 'Closed' ORDER BY [System.CreatedDate] DESC"
time_precisionNoIf True, use time precision for date comparisons in the query.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.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=true and openWorldHint=false, and an output schema documents the return shape. The description adds nothing beyond this: no mention of the server default for `top`, no note that malformed WIQL raises an error, and no hint about result size or pagination.

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. It is efficient, but its brevity reflects under-specification rather than disciplined trimming.

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?

Because annotations cover the safety profile, the schema fully documents all three parameters, and an output schema exists, the minimal description is not harmful. Still, for a query tool whose power depends on WIQL syntax and whose default result cap is server-defined, some operating context would be expected.

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% and each parameter carries its own description plus a WIQL example, so the schema does the heavy lifting. The description contributes no additional meaning about `query`, `top`, or `time_precision`, which is the expected baseline for full coverage.

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?

States a specific verb+resource: execute a WIQL query, return matching work items. That is clearly distinct from sibling CRUD operations like devops_work_item_get, though it never distinguishes itself from devops_work_item_search, which likely overlaps in intent.

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?

There is no when-to-use or when-not-to-use guidance. The only implicit signal is that callers must already possess a WIQL string, and no alternative query tool (e.g., devops_work_item_search) is named or ruled out.

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