Skip to main content
Glama

ado_list_iterations

Retrieve available sprints and iterations from Azure DevOps projects to track development cycles and plan work items.

Instructions

Lista las iteraciones/sprints disponibles en el proyecto

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool 'ado_list_iterations' is registered and implemented in src/index.ts. It fetches iterations using the ADO WIT API and formats them into a tree structure.
    server.tool(
      "ado_list_iterations",
      "Lista las iteraciones/sprints disponibles en el proyecto",
      {},
      async () => {
        const api = await getWitApi();
        const iterations = await api.getClassificationNode(
          currentProject,
          witInterfaces.TreeStructureGroup.Iterations,
          undefined,
          10
        );
    
        function formatIterations(
          node: witInterfaces.WorkItemClassificationNode,
          indent: string = ""
        ): string {
          let result = `${indent}${node.name}`;
          if (node.attributes) {
            const startDate = node.attributes["startDate"];
            const finishDate = node.attributes["finishDate"];
            if (startDate || finishDate) {
              result += ` (${startDate ? new Date(startDate).toLocaleDateString() : "?"} - ${finishDate ? new Date(finishDate).toLocaleDateString() : "?"})`;
            }
          }
          result += "\n";
    
          if (node.children) {
            for (const child of node.children) {
              result += formatIterations(child, indent + "  ");
            }
          }
          return result;
        }
    
        const result = formatIterations(iterations);
    
        return {
          content: [{ type: "text", text: result }],
        };
      }
    );
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 burden of behavioral disclosure. It states the tool lists iterations/sprints but doesn't describe any behavioral traits such as pagination, rate limits, authentication needs, or what happens if no iterations exist. This leaves significant gaps for a tool that likely interacts with a project management system.

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, efficient sentence in Spanish that directly states the tool's purpose without any unnecessary words. It's front-loaded and appropriately sized for a simple listing tool, with zero waste.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list format, fields included) or any behavioral context like error handling. For a tool in a complex server with many siblings, more detail is needed to ensure proper use by an AI agent.

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 input schema has 0 parameters with 100% coverage, so there are no parameters to document. The description appropriately doesn't add parameter details, as none are needed, and it doesn't contradict the schema. This meets the baseline for tools with no parameters.

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 clearly states the action ('Lista las iteraciones/sprints disponibles') and the resource ('en el proyecto'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'ado_query_sprint' or 'ado_query_wiql', which might offer overlapping functionality for sprint-related queries.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'ado_list_iterations' over 'ado_query_sprint' or other query tools, nor does it specify any prerequisites or exclusions for its use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/soulberto/mcp-azure'

If you have feedback or need assistance with the MCP directory API, please join our Discord server