Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AZURE_DEVOPS_ORGNoAzure DevOps organization URL (e.g., https://dev.azure.com/YOUR_ORG). Overrides any configured org.

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

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_work_itemB

Create a work item on the board. type options: Task, Bug, User Story, Epic, Feature.

get_work_itemC

Get a work item by ID.

update_work_itemB

Update state, assignment, or title of a work item.

set_iterationA

Assign a work item to a sprint iteration. Required for items to appear on the Sprint board. Format: 'ProjectName\Sprint N'

query_work_itemsB

Run a WIQL query to find work items. Use for any bulk lookups.

link_work_itemsB

Link two work items. link_type options: Related, Parent, Child, Duplicate, Successor, Predecessor.

get_work_item_relationsB

Get all linked work items. Use after bulk linking to verify hierarchy.

add_commentB

Add a discussion comment to a work item. Use to log agent reasoning or decisions.

list_prsB

List pull requests in a project. status options: active, completed, abandoned, all.

get_prA

Get full details of a specific PR.

create_prC

Create a pull request.

link_pr_to_work_itemA

Link a PR to a work item for full board-to-code traceability. Call every time a PR is raised.

list_branchesC

List all branches in a repository.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 13 tools

Disambiguation5/5

Each tool has a clearly defined purpose with no overlaps. Work item operations are distinct (create, get, update, query, link, set iteration, add comment), PR operations are separate, and branch listing is isolated.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., create_work_item, list_prs, set_iteration). No mixing of conventions or inconsistent naming styles.

Tool Count5/5

13 tools is well-scoped for an Azure DevOps CLI, covering work items (create, read, update, query, link, set iteration, comment) and PRs (create, get, list, link). Each tool serves a clear purpose without excess.

Completeness3/5

Core operations are present (create/read/update for work items, create/read for PRs), but missing delete for work items, update/complete for PRs, and branch creation. Some gaps exist that may hinder full workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues