Skip to main content
Glama
xrmghost

MCP Azure DevOps Server

by xrmghost
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_wiki_page

Retrieve Azure DevOps wiki pages by specifying project, wiki identifier, and page path to access documentation and knowledge base content.

Instructions

Gets a wiki page by its path.

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.

Implementation Reference

  • mcp_azure_devops/azure_devops_client.py:256-262 (handler)
    The core handler function that executes the tool logic by calling the Azure DevOps WikiClient to retrieve the specified wiki page including its content.
    def get_wiki_page(self, project, wiki_identifier, path):
    return self.wiki_client.get_page(
        project=project,
        wiki_identifier=wiki_identifier,
        path=path,
        include_content=True
    )
  • mcp_azure_devops/server.py:334-356 (registration)
    Tool registration in the MCP server, defining the name, description, and input schema for validation.
    types.Tool(
    name="get_wiki_page",
    description="Gets a wiki page by its path.",
    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."
            },
        },
        "required": ["project", "wiki_identifier", "path"],
        "additionalProperties": False
    }
),
  • mcp_azure_devops/server.py:337-356 (schema)
    Input schema definition for the get_wiki_page tool parameters.
        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."
            },
        },
        "required": ["project", "wiki_identifier", "path"],
        "additionalProperties": False
    }
),
  • mcp_azure_devops/server.py:960-966 (handler)
    MCP server dispatch handler that invokes the client method and formats the response for the tool call.
    elif name == "get_wiki_page":
    page = self.client.get_wiki_page(**arguments)
    return {
        "path": page.page.path,
        "url": page.page.url,
        "content": page.page.content,
    }

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't mention whether this is a read-only operation, what authentication is required, what happens if the page doesn't exist, or what format the returned content will have. The description states what the tool does but not 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.

Conciseness5/5

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

The description is a single, efficient sentence that communicates the core functionality without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what gets returned (content, metadata, error conditions), authentication requirements, or how it differs from similar retrieval tools. The context signals indicate this is a 3-parameter tool with no output schema, requiring more descriptive guidance than provided.

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 three parameters (project, wiki_identifier, path) with clear descriptions. The description adds no additional parameter information beyond what's in the schema, 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 clearly states the action ('Gets') and resource ('a wiki page by its path'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_wiki_page_by_title' or 'get_wiki_page_tree', which have similar retrieval purposes but different selection criteria.

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 multiple sibling tools for retrieving wiki content (get_wiki_page_by_title, get_wiki_page_tree, list_wiki_pages, search_wiki_pages), there's no indication of when path-based retrieval is preferred over title-based or other methods.

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