Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

get_wikis

Retrieve wiki details from Azure DevOps projects to access documentation and collaborative content for development teams.

Instructions

Get details of wikis in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdNoThe ID or name of the organization (Default: mycompany)
projectIdNoThe ID or name of the project (Default: MyProject)

Implementation Reference

  • Core handler function that executes the 'get_wikis' tool logic: retrieves wikis from Azure DevOps Wiki API for a given organization and/or project, with comprehensive error handling.
    export async function getWikis(
      connection: WebApi,
      options: GetWikisOptions,
    ): Promise<WikiV2[]> {
      try {
        // Get the Wiki API client
        const wikiApi = await connection.getWikiApi();
    
        // If a projectId is provided, get wikis for that specific project
        // Otherwise, get wikis for the entire organization
        const { projectId } = options;
    
        const wikis = await wikiApi.getAllWikis(projectId);
    
        return wikis || [];
      } catch (error) {
        // Handle resource not found errors specifically
        if (
          error instanceof Error &&
          error.message &&
          error.message.includes('The resource cannot be found')
        ) {
          throw new AzureDevOpsResourceNotFoundError(
            `Resource not found: ${options.projectId ? `Project '${options.projectId}'` : 'Organization'}`,
          );
        }
    
        // If it's already an AzureDevOpsError, rethrow it
        if (error instanceof AzureDevOpsError) {
          throw error;
        }
    
        // Otherwise, wrap it in a generic error
        throw new AzureDevOpsError(
          `Failed to get wikis: ${error instanceof Error ? error.message : String(error)}`,
        );
      }
    }
  • Zod schema for validating input arguments to the 'get_wikis' tool: optional organizationId and projectId.
    export const GetWikisSchema = z.object({
      organizationId: z
        .string()
        .optional()
        .nullable()
        .describe(`The ID or name of the organization (Default: ${defaultOrg})`),
      projectId: z
        .string()
        .optional()
        .nullable()
        .describe(`The ID or name of the project (Default: ${defaultProject})`),
    });
  • Registers the 'get_wikis' tool in the wikisTools array with its name, description, and JSON schema derived from GetWikisSchema.
      name: 'get_wikis',
      description: 'Get details of wikis in a project',
      inputSchema: zodToJsonSchema(GetWikisSchema),
    },
  • Dispatcher handler in handleWikisRequest that parses arguments with GetWikisSchema and invokes the getWikis function, formatting the response for MCP.
    case 'get_wikis': {
      const args = GetWikisSchema.parse(request.params.arguments);
      const result = await getWikis(connection, {
        organizationId: args.organizationId ?? defaultOrg,
        projectId: args.projectId ?? defaultProject,
      });
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
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 only states what the tool does ('Get details') without mentioning permissions, rate limits, pagination, or what 'details' entails (e.g., metadata, content, structure). For a read operation with zero annotation coverage, this lacks critical behavioral context.

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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly, though this conciseness comes at the cost of missing additional 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 multiple sibling tools with overlapping functions, the description is incomplete. It doesn't clarify the tool's scope (e.g., whether it returns a list or detailed objects), differentiate from similar tools, or provide behavioral details needed for effective use in this context.

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 ('organizationId' and 'projectId') documented in the schema as IDs or names with defaults. The description adds no parameter-specific information beyond implying a project context, so it meets the baseline of 3 where the schema handles parameter documentation adequately.

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 ('Get') and resource ('details of wikis in a project'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_wiki_page', 'list_wiki_pages', or 'search_wiki', which all seem related to wikis but with different scopes or functions.

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. With sibling tools like 'get_wiki_page', 'list_wiki_pages', and 'search_wiki', there's no indication of whether this tool retrieves all wikis, specific details, or serves a different purpose, leaving the agent without usage context.

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

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