Skip to main content
Glama

ado_query_area

Query user stories and work items from specific areas in Azure DevOps to track project progress and manage development tasks.

Instructions

Consulta User Stories de un área específica en Azure DevOps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaPathYesRuta del área (ej: 'Proyecto\Equipo')
workItemTypeNoTipo de Work Item (User Story, Bug, Task, etc.)

Implementation Reference

  • The handler implementation for the `ado_query_area` tool, which queries Azure DevOps Work Items based on the provided area path and work item type.
    async ({ areaPath, workItemType }) => {
      const api = await getWitApi();
      const type = workItemType || "User Story";
      const wiql: witInterfaces.Wiql = {
        query: `SELECT [System.Id], [System.Title], [System.State], [System.Tags] FROM WorkItems WHERE [System.WorkItemType] = '${type}' AND [System.AreaPath] UNDER '${areaPath}' ORDER BY [System.Id] DESC`,
      };
    
      const teamContext = { project: currentProject };
      const queryResult = await api.queryByWiql(wiql, teamContext);
      const workItemRefs = queryResult.workItems || [];
    
      if (workItemRefs.length === 0) {
        return {
          content: [
            { type: "text", text: "No se encontraron Work Items en esta área" },
          ],
        };
      }
    
      const ids = workItemRefs.map((wi) => wi.id!).filter((id): id is number => id !== undefined);
      const workItems = await api.getWorkItems(
        ids,
        ["System.Id", "System.Title", "System.State", "System.Tags"]
      );
    
      const result = workItems
        .map((wi) => {
          const fields = wi.fields || {};
          return `ID: ${wi.id} | ${fields["System.Title"]} | Estado: ${fields["System.State"]} | Tags: ${fields["System.Tags"] || "N/A"}`;
        })
        .join("\n");
    
      return {
        content: [{ type: "text", text: result || "Sin resultados" }],
      };
    }
  • src/index.ts:309-318 (registration)
    Registration of the `ado_query_area` tool, including its description and input schema using zod.
    server.tool(
      "ado_query_area",
      "Consulta User Stories de un área específica en Azure DevOps",
      {
        areaPath: z.string().describe("Ruta del área (ej: 'Proyecto\\Equipo')"),
        workItemType: z
          .string()
          .optional()
          .describe("Tipo de Work Item (User Story, Bug, Task, etc.)"),
      },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does ('Consulta User Stories'), but doesn't describe whether this is a read-only operation, what permissions are needed, if there are rate limits, what format the results come in, or any other behavioral characteristics. This leaves significant gaps for an agent to understand how to use it effectively.

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

Conciseness4/5

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

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for what it communicates, though it could be more structured with additional usage context.

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 no annotations, no output schema, and a query tool that likely returns complex work item data, the description is insufficient. It doesn't explain what kind of data is returned, in what format, or any limitations of the query. For a tool with 2 parameters and no structured output documentation, this leaves too many unknowns for effective use.

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?

With 100% schema description coverage, the schema already documents both parameters well ('areaPath' and 'workItemType'). The description doesn't add any additional parameter semantics beyond what's in the schema, so it meets the baseline score of 3 where the schema does the heavy lifting.

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 ('Consulta' - query/retrieve) and resource ('User Stories de un área específica en Azure DevOps'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'ado_query_sprint' or 'ado_query_wiql', which also query Azure DevOps data, so it doesn't reach the highest clarity level.

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 sibling tools like 'ado_query_sprint' (for sprint-based queries) or 'ado_query_wiql' (for custom WIQL queries), nor does it specify prerequisites or exclusions for usage.

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