Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ADO_PATYesPersonal Access Token
ADO_URLYesAzure DevOps URL, e.g. https://server/Collection or https://dev.azure.com/Org
ADO_TEAMNoDefault team for iteration tools<project> Team
ADO_PROJECTNoDefault project
ADO_CA_BUNDLENoPath to a company CA certificate (.pem)
ADO_VERIFY_SSLNoEnable SSL verificationtrue
ADO_API_VERSIONNoAzure DevOps API version: 7.0 for Server 2022 / cloud, 6.0 for Server 2020, 5.0 for Server 20197.0
ADO_ACCESS_LEVELNoAccess level: read, write or fullread
ADO_IGNORE_PROXYNoIgnore HTTP(S)_PROXY, useful for internal serversfalse

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
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_work_item_typesC

Work item types of a project (Bug, Task, User Story, Feature, Test Case, ...).

search_work_itemsA

Search work items of any type.

text: matches the title, or the ID if numeric. work_item_type: one type or several separated by commas, e.g. "Bug, Task". assigned_to / created_by: part of a name, or "@me". tags: one tag or several separated by ";" (all must match). iteration_path / area_path: includes children, e.g. "MyProject\Sprint 12".

query_wiqlB

Run a read-only WIQL query (SELECT ... FROM WorkItems / WorkItemLinks ...) for searches the other tools cannot express. Returns work item summaries.

get_work_itemB

Full details of one work item: description, repro steps, acceptance criteria, scheduling fields and links (parent, children, related, tested by, commits, PRs).

get_work_item_historyB

Change history of a work item: who changed which fields, from what to what.

get_commentsC

Comments (Discussion) of a work item.

list_iterationsC

Team iterations (sprints) with start/finish dates. timeframe: optional filter "past", "current" or "future".

get_task_scheduleC

Scheduling view: start/target dates, estimates, remaining work, overdue flags and remaining work per person.

current_iteration=True uses the team's current sprint. work_item_type: one or several separated by commas, e.g. "Task, Bug".

whoamiA

Check the connection: the signed-in user (owner of the PAT), server URL, access level of this extension and which tools are enabled.

list_projectsB

Projects the PAT can see.

list_teamsC

Teams of a project (team names are used by iteration and schedule tools).

list_team_membersD

Members of a team.

list_pipelinesB

Pipelines (build definitions) of a project; name_filter supports * wildcards.

list_pipeline_runsB

Recent runs (builds), newest first. status: inProgress, completed, notStarted, ... result: succeeded, failed, canceled, partiallySucceeded.

get_pipeline_runB

Details of one run, including failed or warning steps with their error messages.

get_pipeline_logA

Log of a run. Without log_id, returns the last lines of every failed step. (log_id values come from get_pipeline_run.)

list_repositoriesB

Git repositories (of one project, or of all visible projects if no project is set).

list_branchesC

Branches of a repository; name_filter matches the start of the branch name.

browse_repositoryB

List files and folders in a repository folder (one level).

get_file_contentC

Content of a text file in a repository (truncated to max_chars).

list_commitsB

Recent commits of a repository, optionally for a branch, author or file/folder path.

list_pull_requestsB

Pull requests of a project (or one repository). status: active, completed, abandoned or all. created_by: part of a name.

get_pull_requestB

Details of a pull request: description, reviewers and votes, linked work items.

search_test_casesB

Search Test Case work items by title text, state, owner ("@me"), tags, area or iteration.

get_test_caseC

One test case with its parsed steps (action / expected result).

list_test_plansC

Test plans of a project.

list_test_suitesC

Suites of a test plan, with parent suite ids to rebuild the tree.

get_suite_test_resultsB

Test points of a suite: each test case per configuration with tester and last outcome (Passed / Failed / Blocked / NotApplicable / NotRun), plus a summary count.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.6/5.0

Scored across 28 tools

Disambiguation4/5

Most tools are clearly separated by Azure DevOps subdomain and action: work items, pipelines, repositories, tests, teams. There is minor overlap between search_work_items, search_test_cases, and query_wiql as multiple search entry points, but the descriptions generally make the intended use clear.

Naming Consistency4/5

The set uses a consistent snake_case verb_noun pattern such as get_work_item, list_pipeline_runs, and search_test_cases. whoami is the only meaningful deviation, but it is a conventional identity command and remains understandable.

Tool Count2/5

At 28 tools, the surface is heavy and exceeds the well-scoped range, even for a broad platform like Azure DevOps. While many tools serve distinct domains, the total volume increases selection burden for an agent.

Completeness2/5

The surface is almost entirely read-only: there are no create, update, delete, queue-pipeline, or PR mutation operations. Even if read-only inspection is intentional, notable read gaps remain such as PR file/thread details and repository code search.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues