Skip to main content
Glama
stefanskiasan

Azure DevOps MCP Server for Cline

create_wiki

Create a new wiki in Azure DevOps projects to document processes, share knowledge, and organize team information.

Instructions

Create a new wiki

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWiki name
projectIdNoProject ID (optional, defaults to current project)
mappedPathNoMapped path (optional, defaults to /)

Implementation Reference

  • The core handler function implementing the create_wiki tool logic: validates input, initializes Azure DevOps connection, creates wiki via API, handles errors, and formats MCP response.
    export async function createWiki(args: CreateWikiArgs, config: AzureDevOpsConfig) {
      if (!args.name) {
        throw new McpError(ErrorCode.InvalidParams, 'Wiki name is required');
      }
    
      AzureDevOpsConnection.initialize(config);
      const connection = AzureDevOpsConnection.getInstance();
      const wikiApi = await connection.getWikiApi();
    
      try {
        const wikiCreateParams = {
          name: args.name,
          projectId: args.projectId || config.project,
          mappedPath: args.mappedPath || '/',
          type: WikiType.ProjectWiki,
        };
    
        const wiki = await wikiApi.createWiki(wikiCreateParams, config.project);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(wiki, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        if (error instanceof McpError) throw error;
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to create wiki: ${errorMessage}`
        );
      }
    }
  • MCP input schema definition for the create_wiki tool, including properties, descriptions, and required fields.
    {
      name: 'create_wiki',
      description: 'Create a new wiki',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Wiki name',
          },
          projectId: {
            type: 'string',
            description: 'Project ID (optional, defaults to current project)',
          },
          mappedPath: {
            type: 'string',
            description: 'Mapped path (optional, defaults to /)',
          },
        },
        required: ['name'],
      },
  • Registration of the createWiki handler within the wikiTools module, wrapping the core createWiki function.
    createWiki: (args: { name: string; projectId?: string; mappedPath?: string }) =>
      createWiki(args, config),
  • src/index.ts:145-146 (registration)
    Top-level tool dispatch registration in the main server switch statement.
    case 'create_wiki':
      result = await tools.wiki.createWiki(request.params.arguments);
  • TypeScript interface defining arguments for createWiki, matching the tool schema.
    interface CreateWikiArgs {
      name: string;
      projectId?: string;
      mappedPath?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create a new wiki' which implies a write/mutation operation, but doesn't cover permissions needed, whether creation is idempotent, what happens on conflicts, or what the response looks like. This is inadequate for a mutation 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 extremely concise at three words, front-loading the core action without any fluff. Every word earns its place, though this brevity contributes to gaps in other dimensions.

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 this is a mutation tool with no annotations, no output schema, and sibling tools that suggest a wiki management context, the description is incomplete. It doesn't explain what a 'wiki' is in this system, what gets created, or how it relates to other wiki tools, leaving significant gaps for an agent.

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?

The schema description coverage is 100%, so the schema already documents all three parameters (name, projectId, mappedPath) with their types and optionality. The description adds no parameter-specific information beyond what's in the schema, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new wiki' states the basic action (create) and resource (wiki), but it's vague about what a 'wiki' entails in this context and doesn't distinguish it from sibling tools like 'create_work_item' or 'update_wiki_page'. It provides minimal but functional purpose information.

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 offers no guidance on when to use this tool versus alternatives like 'update_wiki_page' or 'get_wikis', nor does it mention prerequisites such as needing a project context. It's a bare statement with no contextual usage information.

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

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