azure-boards-mcp-testcases
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZDO_ORG | Yes | The Azure DevOps organization name. | |
| AZDO_PAT | Yes | Personal Access Token with 'Work Items Read' scope. | |
| AZDO_PROJECT | Yes | The Azure DevOps project name. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_azure_boards_work_itemA | Fetches Azure Boards work item details from a work item ID or URL for QA test case generation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no risk of overlap or misselection. The tool's name and description clearly define a single purpose.
The single tool folows a consistent verb_noun pattern, using 'get_*' which is clear and predictable.
One tool feels thin for a server named 'azcool-boards-mcp-testcases', which implies a broader test case generation workflow. The count is borderline but not extreme.
Covers only a single fetch operation, which is insufficient to generate test cases. The surface lacks listing, selection, or generation tooling, leaving significant workflow gaps.