Skip to main content
Glama

ado_list_areas

List available project areas in Azure DevOps to organize work items and track development progress effectively.

Instructions

Lista las áreas disponibles en el proyecto

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registration and handler implementation for the ado_list_areas tool. It uses getWitApi to fetch area nodes and then formats them into a readable text tree.
    server.tool(
      "ado_list_areas",
      "Lista las áreas disponibles en el proyecto",
      {},
      async () => {
        const api = await getWitApi();
        const areas = await api.getClassificationNode(
          currentProject,
          witInterfaces.TreeStructureGroup.Areas,
          undefined,
          10
        );
    
        function formatAreas(
          node: witInterfaces.WorkItemClassificationNode,
          indent: string = ""
        ): string {
          let result = `${indent}${node.name}\n`;
          if (node.children) {
            for (const child of node.children) {
              result += formatAreas(child, indent + "  ");
            }
          }
          return result;
        }
    
        const result = formatAreas(areas);
    
        return {
          content: [{ type: "text", text: result }],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning permissions, rate limits, pagination, or response format. For a list operation, this lack of detail is a significant gap in transparency.

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 wasted words. It's front-loaded and appropriately sized for a simple list tool.

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 complexity (a list operation with no output schema and no annotations), the description is incomplete. It lacks details on what the output includes (e.g., area names, IDs, hierarchy) and behavioral aspects like error handling or scope, making it insufficient for full contextual understanding.

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 no parameter documentation is needed. The description doesn't add parameter details, which is acceptable here, but it doesn't compensate for any gaps since there are none, warranting a baseline score above 3.

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 áreas disponibles') and the resource ('en el proyecto'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'ado_query_area', which might also retrieve area information, so it doesn't fully distinguish itself from alternatives.

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 guidance is provided on when to use this tool versus alternatives such as 'ado_query_area' or 'ado_query_wiql'. The description implies it lists areas, but it doesn't specify contexts like retrieving all areas versus filtered queries, leaving usage unclear.

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