Skip to main content
Glama
nikydobrev

Azure DevOps Multi-Organization MCP Server

by nikydobrev

list_organizations

Retrieve all configured Azure DevOps organizations to manage pipelines, builds, and repositories across multiple accounts without switching contexts.

Instructions

Lists all available Azure DevOps organizations from the configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Inline handler function for the list_organizations tool. Retrieves available organizations from the ConnectionManager and returns them as a formatted JSON text response.
    async () => {
      const orgs = connectionManager.getAvailableOrganizations();
      return {
        content: [{ type: "text", text: JSON.stringify(orgs, null, 2) }],
      };
    }
  • Registration of the list_organizations tool on the MCP server, including name, description, empty input schema, and inline handler.
    server.tool(
      "list_organizations",
      "Lists all available Azure DevOps organizations from the configuration",
      {},
      async () => {
        const orgs = connectionManager.getAvailableOrganizations();
        return {
          content: [{ type: "text", text: JSON.stringify(orgs, null, 2) }],
        };
      }
    );
  • Helper method in ConnectionManager that provides the list of available organizations by delegating to ConfigLoader.
    public getAvailableOrganizations(): string[] {
      return this.configLoader.getOrganizations();
    }
  • Higher-level tool registration function that invokes registerOrganizationTools (among others) to set up all tools.
    export function registerTools(server: McpServer, connectionManager: ConnectionManager) {
      registerOrganizationTools(server, connectionManager);
      registerPipelineTools(server, connectionManager);
      registerRepositoryTools(server, connectionManager);
    }
  • src/index.ts:14-14 (registration)
    Top-level call to register all tools, including list_organizations indirectly via the chain.
    registerTools(server, connectionManager);
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 mentions 'from the configuration', hinting at data source, but fails to describe critical traits like authentication needs, rate limits, pagination, or response format. This is inadequate for a tool with zero annotation coverage.

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 that directly states the tool's purpose without any fluff. It is front-loaded and appropriately sized, making it easy for an agent to parse quickly.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks depth. It does not explain return values or behavioral aspects, which could be important for integration. However, for a basic list operation, it meets the minimum viable threshold.

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, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately does not discuss parameters, aligning with the schema's completeness. A baseline of 4 is applied as it compensates for the lack of parameters by not adding unnecessary information.

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 'Lists' and the resource 'Azure DevOps organizations from the configuration', making the purpose specific and understandable. However, it does not explicitly distinguish this tool from sibling tools like 'list_projects', which might cause confusion about scope differentiation.

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, such as 'list_projects' or other sibling tools. It lacks context about prerequisites, timing, or exclusions, leaving the agent with minimal usage direction.

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/nikydobrev/mcp-server-azure-devops-multi'

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