Skip to main content
Glama
mmruesch12
by mmruesch12

list_projects

Retrieve a list of all accessible projects within an Azure DevOps organization to manage and organize development workflows effectively.

Instructions

List all accessible projects in the Azure DevOps organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that parses input, fetches projects using coreClient.getProjects(), and returns them as JSON text content.
    export async function listProjects(rawParams: any) {
      // Parse arguments
      const params = listProjectsSchema.parse(rawParams);
    
      console.error("[API] Listing projects");
    
      try {
        // Get the Core API client
        const coreClient = await getCoreClient();
    
        // Get projects
        const projects = await coreClient.getProjects();
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(projects, null, 2),
            },
          ],
        };
      } catch (error) {
        logError("Error listing projects", error);
        throw error;
      }
    }
  • Zod schema for list_projects input parameters (empty object) and inferred TypeScript type.
    export const listProjectsSchema = z.object({});
    
    export type ListProjectsParams = z.infer<typeof listProjectsSchema>;
  • Tool registration metadata including name, description, and input schema, part of the projectTools array exported for server use.
      name: "list_projects",
      description:
        "List all accessible projects in the Azure DevOps organization",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • src/index.ts:97-98 (registration)
    Dispatch case in the main CallToolRequest handler that invokes the listProjects function.
    case "list_projects":
      return await listProjects(request.params.arguments || {});
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 states it's a list operation but doesn't describe return format, pagination, sorting, filtering, or access control details. 'Accessible projects' hints at permissions but lacks specifics. For a list tool with zero annotation coverage, this is insufficient.

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?

Single sentence, front-loaded with core action, zero waste. Every word earns its place: 'List' (action), 'all accessible projects' (scope/resource), 'Azure DevOps organization' (context). Efficient and structured.

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?

Given zero parameters, no output schema, and no annotations, the description is minimally adequate but lacks details on return format, pagination, or error handling. For a list operation in a complex DevOps context, more completeness would help agents use it effectively.

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 tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to compensate for missing param info, and it correctly implies no inputs are required. Baseline is 4 for zero-parameter tools when description aligns.

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 verb ('List') and resource ('all accessible projects'), specifying the scope ('in the Azure DevOps organization'). It distinguishes from siblings like 'get_project' (singular) and 'list_pull_requests' (different resource). However, it doesn't explicitly differentiate from other list tools like 'list_work_items' beyond resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('accessible projects') but doesn't provide explicit guidance on when to use this vs. alternatives like 'get_project' for single project details or other list tools. No exclusions or prerequisites are mentioned, leaving usage decisions to inference.

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

Related 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/mmruesch12/azdo-mcp'

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