Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_repository_details

Retrieve detailed Azure DevOps repository information including statistics and refs to inspect metadata, branches, and tags.

Instructions

Get detailed information about a repository including statistics and refs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe ID or name of the project (Default: MyProject)
refFilterNoOptional filter for refs (e.g., "heads/" or "tags/")
branchNameNoName of specific branch to get statistics for (if includeStatistics is true)
includeRefsYesWhether to include repository refs
repositoryIdYesThe ID or name of the repository
organizationIdNoThe ID or name of the organization (Default: mycompany)
includeStatisticsYesWhether to include branch statistics

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • changedInput schema / required
      Previous value: -[
-  "repositoryId"
-]New value: +[
+  "repositoryId",
+  "includeStatistics",
+  "includeRefs"
+]
  2. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / organizationId
      Added value: +{
+  "description": "The ID or name of the organization (Default: mycompany)",
+  "type": "string"
+}
    • changedInput schema / properties / projectId / description
      Previous value: -"The ID or name of the project"New value: +"The ID or name of the project (Default: MyProject)"
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "repositoryId"
-]New value: +[
+  "repositoryId"
+]
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation via 'Get' and mentions statistics and refs, but does not disclose permissions, side effects, rate limits, or return behavior.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no wasted words. It efficiently communicates the core purpose and the main optional data categories.

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?

For a tool with seven parameters, no annotations, and no output schema, the description is too sparse. It does not clarify what 'detailed information' returns beyond statistics and refs, nor does it explain required parameters or access expectations.

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%, so every parameter already has a documented meaning in the schema. The description adds only a high-level mention of statistics and refs, which does not provide syntax or filtering detail beyond the schema.

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?

The description states a clear verb and resource: retrieving detailed repository information including statistics and refs. It distinguishes itself from list-style siblings implicitly, but does not explicitly distinguish itself from near siblings such as get_repository or get_project_details.

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 explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The inclusion of statistics and refs implies a use case, but the agent must infer that from the description alone.

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

Deploy Server

Other Tools