Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_commits

Fetch commits on a branch, including file-level diff content for each commit.

Instructions

List recent commits on a branch including file-level diff content for each commit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMaximum number of commits to return (Default: 10)
skipNoNumber of commits to skip from the newest
projectIdNoThe ID or name of the project (Default: MyProject)
branchNameYesBranch name to list commits from
repositoryIdYesThe ID or name of the repository
organizationIdNoThe ID or name of the organization (Default: mycompany)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • addedInput schema / properties / skip / maximum
      Added value: +9007199254740991
  2. Addedv1.0.0

TDQS

B3.3/5.0
Behavior3/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 discloses that results include file-level diff content, which is useful return behavior, and 'List' implies a read operation. However, it omits permissions, pagination/limit behavior, side effects, and rate context.

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?

A single front-loaded sentence with no wasted words. It efficiently combines the operation, scope, and key return detail.

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

Completeness3/5

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

No output schema and no annotations exist, so the description should fill more gaps. It notes diff content but does not describe result structure, pagination, or auth defaults; parameters are covered by schema, but output context remains thin.

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 the baseline is 3. The description only echoes branch scope and does not add syntax, defaults, constraints, or meaning beyond what the schema already documents.

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?

States a specific verb (List) and resource (recent commits) plus the branch scope and that file-level diff content is included. It is clearly distinct from create_commit by verb, but does not explicitly name alternatives or differentiate from other read/list siblings.

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?

No when-to-use guidance, prerequisites, or alternatives are provided. An agent can infer it lists commits, but the description does not say when to choose it over related read tools such as get_pull_request_changes or search_code.

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