Skip to main content
Glama
ennuiii

Azure DevOps MCP Server with PAT Authentication

by ennuiii

wiki_list_wikis

Retrieve a list of wikis for Azure DevOps organizations or specific projects using PAT authentication. Simplify wiki management by filtering results by project name or ID.

Instructions

Retrieve a list of wikis for an organization or project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoThe project name or ID to filter wikis. If not provided, all wikis in the organization will be returned.

Implementation Reference

  • The core handler logic for the "wiki_list_wikis" tool. It uses the Azure DevOps WikiApi to fetch all wikis for the given project (or organization-wide if no project specified), and returns the JSON serialized list or an error message.
    async ({ project }) => {
      try {
        const connection = await connectionProvider();
        const wikiApi = await connection.getWikiApi();
        const wikis = await wikiApi.getAllWikis(project);
    
        if (!wikis) {
          return { content: [{ type: "text", text: "No wikis found" }], isError: true };
        }
    
        return {
          content: [{ type: "text", text: JSON.stringify(wikis, null, 2) }],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : "Unknown error occurred";
    
        return {
          content: [{ type: "text", text: `Error fetching wikis: ${errorMessage}` }],
          isError: true,
        };
      }
  • Input schema definition for the tool using Zod, with optional 'project' parameter.
    {
      project: z.string().optional().describe("The project name or ID to filter wikis. If not provided, all wikis in the organization will be returned."),
    },
  • Direct registration of the "wiki_list_wikis" tool on the McpServer instance within configureWikiTools.
    server.tool(
      WIKI_TOOLS.list_wikis,
      "Retrieve a list of wikis for an organization or project.",
      {
        project: z.string().optional().describe("The project name or ID to filter wikis. If not provided, all wikis in the organization will be returned."),
      },
      async ({ project }) => {
        try {
          const connection = await connectionProvider();
          const wikiApi = await connection.getWikiApi();
          const wikis = await wikiApi.getAllWikis(project);
    
          if (!wikis) {
            return { content: [{ type: "text", text: "No wikis found" }], isError: true };
          }
    
          return {
            content: [{ type: "text", text: JSON.stringify(wikis, null, 2) }],
          };
        } catch (error) {
          const errorMessage = error instanceof Error ? error.message : "Unknown error occurred";
    
          return {
            content: [{ type: "text", text: `Error fetching wikis: ${errorMessage}` }],
            isError: true,
          };
        }
      }
  • Constant mapping internal name to tool name string "wiki_list_wikis" in WIKI_TOOLS object.
    list_wikis: "wiki_list_wikis",
  • src/tools.ts:26-26 (registration)
    Invocation of configureWikiTools in configureAllTools, which registers the wiki tools including "wiki_list_wikis".
    configureWikiTools(server, tokenProvider, connectionProvider);
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 the tool retrieves a list but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what happens if no wikis exist. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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, clear sentence with zero waste—it directly states the tool's purpose without redundancy. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 low complexity (one optional parameter) and high schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it lacks details on return values (e.g., list structure, fields) and behavioral context, which could hinder an agent's ability to use it effectively beyond basic invocation.

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 the single parameter 'project' fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when 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 ('Retrieve a list') and resource ('wikis'), specifying it's for an organization or project. It distinguishes from siblings like 'wiki_get_wiki' (single wiki) and 'wiki_list_pages' (pages within a wiki), but doesn't explicitly contrast with 'search_wiki' which might have overlapping functionality.

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 explicit guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'search_wiki' (which could filter wikis) or 'core_list_projects' (which lists projects, not wikis). The description implies usage for listing wikis but lacks context about prerequisites or exclusions.

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/ennuiii/DevOpsMcpPAT'

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