Skip to main content
Glama

create_wiki

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

Instructions

Creates a new wiki in a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
nameYesThe name of the wiki to create.

Implementation Reference

  • The handler in the MCP server's _execute_tool method that handles calls to the 'create_wiki' tool by invoking the client's create_wiki method and formatting the response.
    elif name == "create_wiki":
        wiki = self.client.create_wiki(**arguments)
        return {
            "id": wiki.id,
            "name": wiki.name,
            "url": wiki.url,
            "remote_url": wiki.remote_url,
        }
  • The input schema definition for the 'create_wiki' tool, specifying parameters project and name.
    inputSchema={
        "type": "object",
        "properties": {
            "project": {
                "type": "string", 
                "description": "The name or ID of the project."
            },
            "name": {
                "type": "string", 
                "description": "The name of the wiki to create."
            },
        },
        "required": ["project", "name"],
        "additionalProperties": False
  • Registration of the 'create_wiki' tool in the server's tool list, including name, description, and schema.
    types.Tool(
        name="create_wiki",
        description="Creates a new wiki in a project.",
        inputSchema={
            "type": "object",
            "properties": {
                "project": {
                    "type": "string", 
                    "description": "The name or ID of the project."
                },
                "name": {
                    "type": "string", 
                    "description": "The name of the wiki to create."
                },
            },
            "required": ["project", "name"],
            "additionalProperties": False
        }
    ),
  • The core implementation of wiki creation in the AzureDevOpsClient class, which calls the Azure DevOps API to create a new wiki.
    def create_wiki(self, project, name):
        project_object = self.core_client.get_project(project)
        wiki_params = WikiCreateParametersV2(name=name, type='projectWiki', project_id=project_object.id)
        return self.wiki_client.create_wiki(wiki_create_params=wiki_params, project=project)
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 'creates' which implies a write operation, but doesn't disclose behavioral traits like required permissions, whether this is idempotent, what happens on duplicate names, or error conditions. For a creation tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for a simple creation tool, though it could be slightly more informative without losing conciseness. Every word earns its place.

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 and no output schema, the description is incomplete for a creation tool. It doesn't explain what the tool returns (e.g., wiki ID, success status) or address behavioral aspects like error handling. With 2 parameters and 100% schema coverage, the input is covered, but overall context for safe and effective use is lacking.

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 both parameters ('project' and 'name') with clear descriptions. The description adds no additional meaning beyond what's in the schema—it doesn't explain parameter relationships, constraints, or examples. With high schema coverage, 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 clearly states the action ('creates') and resource ('new wiki in a project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_or_update_wiki_page_smart' or 'create_wiki_page', which creates wikis at different granularities. The description is specific but lacks sibling distinction.

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 siblings like 'create_wiki_page' (for individual pages) and 'create_or_update_wiki_page_smart' (for smart updates), there's no indication of context, prerequisites, or exclusions. Usage is implied by the name but not explicitly stated.

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

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