Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_wiki

Create a new Azure DevOps project wiki or code wiki, letting AI assistants add documentation spaces to projects via the MCP server.

Instructions

Create a new wiki in the project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the new wiki
typeYesType of wiki to create (projectWiki or codeWiki)projectWiki
projectIdNoThe ID or name of the project (Default: MyProject)
mappedPathYesFolder path inside repository which is shown as Wiki (only for codeWiki)/
repositoryIdNoThe ID of the repository to associate with the wiki (required for codeWiki)
organizationIdNoThe ID or name of the organization (Default: mycompany)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.0.6
    • removedInput schema / properties / mappedPath / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / mappedPath / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / organizationId / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / organizationId / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / projectId / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / projectId / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / repositoryId / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / repositoryId / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "type",
+  "mappedPath"
+]
  2. Addedv1.0.0

TDQS

C2.9/5.0
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 behavioral burden. It only says a wiki is created in the project, without stating permissions needed, side effects, reversibility, or whether codeWiki requires a repository. This is minimal for a mutation tool.

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, front-loaded sentence with no wasted words. It is appropriately sized for the core action, though it omits necessary detail.

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 six parameters, three required, an enum, and type-dependent requirements (e.g., repositoryId required for codeWiki), the description is far too incomplete. It does not address the two wiki types, defaults, or the repository association needed for codeWiki.

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%, so the schema already documents all six parameters thoroughly. The description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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 states a specific verb ('Create') and resource ('wiki'), clearly distinguishing it from creation of other resources. However, it does not distinguish itself from sibling tools like create_wiki_page, which is also about wiki content creation.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description only restates the action; it does not help an agent choose between create_wiki and create_wiki_page, or understand required context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools