Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

List repositories

devops_repository_list
Read-only

Lists repositories in an on-premises Azure DevOps organization so AI assistants can browse projects and select codebases for review or automation.

Instructions

Get the list of repositories.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "devops_repository_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/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, so the safety profile is covered; the description contributes nothing beyond that. It does not say whether the result is paginated, whether it returns all repositories the caller can see, or whether it requires authentication context — the kind of context that would justify a higher score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and contains no padding, so it is concise. However, that brevity comes at the cost of usefulness — it is terse to the point of being a restatement of the title rather than an informative sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inputs and outputs are simple and the output schema exists, so a long description is not required, but the definition still leaves the key unknown — the scope of 'list' (all repositories vs. those in a project/org) — unaddressed. For a tool an agent must pick out of a large catalog, that omission matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline for a parameterless tool applies. Nothing in the description misrepresents the input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description reads 'Get the list of repositories', which almost verbatim restates the tool name and title ('devops_repository_list' / 'List repositories'). It does establish the resource (repositories) but adds no scope detail, such as whether it lists organization-wide or project-scoped repositories, so an agent gets no differentiation from siblings like devops_repository_get beyond the word 'list'.

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 guidance, no exclusions, and no mention of any alternative tool (for example devops_repository_get for a single repository or devops_code_search for finding content). The agent must infer usage entirely from the tool name.

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