Skip to main content
Glama

create_or_update_wiki_page_smart

Create or update Azure DevOps wiki pages automatically by specifying project, wiki, path, and content parameters to maintain documentation.

Instructions

Creates a new wiki page or updates existing one intelligently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.
pathYesThe path of the wiki page.
contentYesThe content of the wiki page.

Implementation Reference

  • The core handler function that executes the tool logic: intelligently creates or updates a wiki page by first trying a safe update and falling back to creation if the page does not exist (404 error).
    def create_or_update_wiki_page_smart(self, project, wiki_identifier, path, content):
        """
        Creates a new wiki page or updates existing one intelligently.
        """
        try:
            # Try to update first
            return self.update_wiki_page_safe(project, wiki_identifier, path, content)
        except Exception as e:
            if "not found" in str(e).lower() or "404" in str(e):
                # Page doesn't exist, create it
                return self.create_wiki_page(project, wiki_identifier, path, content)
            else:
                raise e
  • Registers the tool in the MCP server's tools list, including its name, description, and input schema.
    types.Tool(
        name="create_or_update_wiki_page_smart",
        description="Creates a new wiki page or updates existing one intelligently.",
        inputSchema={
            "type": "object",
            "properties": {
                "project": {
                    "type": "string", 
                    "description": "The name or ID of the project."
                },
                "wiki_identifier": {
                    "type": "string", 
                    "description": "The name or ID of the wiki."
                },
                "path": {
                    "type": "string", 
                    "description": "The path of the wiki page."
                },
                "content": {
                    "type": "string", 
                    "description": "The content of the wiki page."
                },
            },
            "required": ["project", "wiki_identifier", "path", "content"],
            "additionalProperties": False
        }
    ),
  • Defines the input schema for validating the tool's parameters: project, wiki_identifier, path, and content.
    inputSchema={
        "type": "object",
        "properties": {
            "project": {
                "type": "string", 
                "description": "The name or ID of the project."
            },
            "wiki_identifier": {
                "type": "string", 
                "description": "The name or ID of the wiki."
            },
            "path": {
                "type": "string", 
                "description": "The path of the wiki page."
            },
            "content": {
                "type": "string", 
                "description": "The content of the wiki page."
            },
        },
        "required": ["project", "wiki_identifier", "path", "content"],
        "additionalProperties": False
    }
  • Server-side dispatch logic that calls the client handler with arguments and formats the response for MCP protocol.
    elif name == "create_or_update_wiki_page_smart":
        page = self.client.create_or_update_wiki_page_smart(**arguments)
        return {
            "path": page.page.path,
            "url": page.page.url,
            "content": page.page.content,
            "message": "Wiki page created or updated successfully."
        }
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 the tool 'creates or updates' intelligently, which implies mutation but doesn't specify what 'intelligently' entails (e.g., automatic conflict resolution, versioning, or permissions). No information is provided about side effects, error handling, or response format.

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 that directly states the tool's purpose. It's front-loaded with the core action and includes the key qualifier 'intelligently' without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'intelligently' means operationally, lacks details on behavioral traits like error conditions or side effects, and provides no guidance on usage versus siblings, leaving significant gaps for an agent to understand the tool fully.

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 fully documents all 4 parameters. The description adds no parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for adequate coverage without extra value.

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 ('creates or updates') and resource ('wiki page'), and specifies the intelligent behavior. However, it doesn't distinguish this from sibling tools like 'create_wiki_page' or 'update_wiki_page', which have similar purposes but lack the 'intelligently' qualifier.

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 like 'create_wiki_page' or 'update_wiki_page'. It mentions 'intelligently' but doesn't explain what this means in practice or when it's preferable over simpler create/update operations.

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