Skip to main content
Glama
uright

Azure DevOps Wiki MCP Server

by uright

list_wiki

Retrieve all wikis available in an Azure DevOps project to identify and access documentation repositories for content management.

Instructions

List all wikis in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationNoAzure DevOps organization name
projectNoProject name

Implementation Reference

  • The primary handler for the 'list_wiki' tool. Parses input using WikiListRequestSchema, initializes client if needed, calls client.listWikis(), and returns JSON-formatted list of wikis.
    private async handleListWiki(args: any) {
      const request = WikiListRequestSchema.parse(args);
      const organization = request.organization || this.config.defaultOrganization;
      const project = request.project || this.config.defaultProject;
      
      if (!organization) {
        throw new Error('Organization is required either as parameter or in server configuration');
      }
      if (!project) {
        throw new Error('Project is required either as parameter or in server configuration');
      }
      
      const client = await this.getClient(organization, project);
      const wikis = await client.listWikis(request);
      
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(wikis, null, 2)
        }]
      };
    }
  • Zod schema for validating input parameters to the list_wiki tool (organization and project are optional).
    export const WikiListRequestSchema = z.object({
      organization: z.string().min(1).optional(),
      project: z.string().min(1).optional(),
    });
  • src/server.ts:138-155 (registration)
    Registration of the 'list_wiki' tool in the MCP server's ListToolsRequestHandler, including name, description, and input schema definition.
    {
      name: 'list_wiki',
      description: 'List all wikis in a project',
      inputSchema: {
        type: 'object',
        properties: {
          organization: {
            type: 'string',
            description: 'Azure DevOps organization name'
          },
          project: {
            type: 'string',
            description: 'Project name'
          }
        },
        required: []
      }
    }
  • Helper method in AzureDevOpsWikiClient that performs the actual API call to Azure DevOps WikiApi.getAllWikis(project) and maps the response to WikiInfo[] format.
    async listWikis(request: WikiListRequest): Promise<WikiInfo[]> {
      if (!this.wikiApi || !this.connection) {
        throw new Error('Azure DevOps client not initialized');
      }
    
      try {
        const organization = request.organization || this.config.organization;
        const project = request.project || this.config.project;
        
        if (!organization || !project) {
          throw new Error('Organization and project must be provided');
        }
    
        const wikis = await this.wikiApi.getAllWikis(project);
        
        if (!wikis || !Array.isArray(wikis)) {
          return [];
        }
    
        return wikis.map(wiki => ({
          id: wiki.id || '',
          name: wiki.name || '',
          type: wiki.type?.toString() || '',
          url: wiki.url || '',
          project: project,
          repositoryId: wiki.repositoryId || '',
          mappedPath: wiki.mappedPath || ''
        }));
    
      } catch (error) {
        throw new Error(`Failed to list wikis: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • TypeScript interface defining the structure of WikiInfo objects returned by the list_wiki tool.
    export interface WikiInfo {
      id: string;
      name: string;
      type: string;
      url: string;
      project: string;
      repositoryId: string;
      mappedPath: string;
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'List all wikis' but doesn't disclose behavioral traits such as pagination, rate limits, authentication needs, or what 'all wikis' entails (e.g., scope, 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 with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 simple input schema, the description is incomplete. It lacks details on behavior (e.g., how wikis are listed, error handling) and doesn't compensate for the absence of structured data, making it insufficient for effective tool 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?

Schema description coverage is 100%, with both parameters ('organization' and 'project') documented in the schema. The description adds no additional meaning beyond implying these parameters are used to specify the project context, so it meets the baseline 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 ('List all wikis') and target resource ('in a project'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'search_wiki' or 'wiki_get_page_tree' that might also retrieve wiki information, so it misses the top score.

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 like 'search_wiki' or 'wiki_get_page_tree'. It mentions the context ('in a project') but offers no explicit when/when-not instructions or prerequisites, leaving usage unclear relative to siblings.

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/uright/azure-devops-wiki-mcp'

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