Skip to main content
Glama
xrmghost

MCP Azure DevOps Server

by xrmghost
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_wiki_page_tree

Retrieve the hierarchical structure of Azure DevOps wiki pages to improve navigation and organization within projects.

Instructions

Get hierarchical structure of wiki pages for better navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.

Implementation Reference

  • mcp_azure_devops/azure_devops_client.py:393-419 (handler)
    The handler function that executes the tool logic: lists wiki pages and builds a nested dictionary representing the hierarchical page tree.
    def get_wiki_page_tree(self, project, wiki_identifier):
    """
    Get hierarchical structure of wiki pages.
    """
    pages = self.list_wiki_pages(project, wiki_identifier)
    
    # Organize pages into a tree structure
    tree = {}
    for page in pages:
        path_parts = page["path"].strip("/").split("/")
        current_level = tree
        
        for i, part in enumerate(path_parts):
            if part not in current_level:
                current_level[part] = {
                    "children": {},
                    "info": None
                }
            
            if i == len(path_parts) - 1:
                # This is the final part, store page info
                current_level[part]["info"] = page
            
            current_level = current_level[part]["children"]
    
    return tree
  • mcp_azure_devops/server.py:673-687 (schema)
    Input schema definition for the get_wiki_page_tree tool, validating required parameters project and wiki_identifier.
    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."
        },
    },
    "required": ["project", "wiki_identifier"],
    "additionalProperties": False
}
  • mcp_azure_devops/server.py:1023-1024 (registration)
    Registration and dispatch logic in the tool execution handler that routes calls to the client.get_wiki_page_tree method.
    elif name == "get_wiki_page_tree":
    return self.client.get_wiki_page_tree(**arguments)
  • mcp_azure_devops/server.py:670-688 (registration)
    The tool object definition and registration in the server's tools list.
    types.Tool(
    name="get_wiki_page_tree",
    description="Get hierarchical structure of wiki pages for better navigation.",
    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."
            },
        },
        "required": ["project", "wiki_identifier"],
        "additionalProperties": False
    }
),

Tool Definition Quality

B3.1/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 full burden. It mentions 'hierarchical structure' but doesn't disclose behavioral traits such as read-only nature, potential rate limits, authentication needs, output format (e.g., JSON tree), or error handling. For a tool with no annotation coverage, this is a significant gap in transparency.

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?

Single sentence, front-loaded with the core purpose, and zero waste. Every word earns its place by succinctly conveying the tool's function and benefit ('for better navigation').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 2 parameters with full schema coverage and no output schema, the description is minimally adequate but incomplete. It lacks details on behavioral context (e.g., read-only, format) and doesn't compensate for the absence of annotations or output schema, leaving gaps in understanding how to interpret results.

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%, with both parameters ('project' and 'wiki_identifier') well-documented in the schema. The description adds no additional meaning about parameters beyond implying they identify the wiki for navigation. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Get') and resource ('hierarchical structure of wiki pages'), specifying the purpose is for navigation. It distinguishes from siblings like 'get_wiki_page' (single page) or 'list_wiki_pages' (flat list), though not explicitly named. However, it lacks specificity on what 'hierarchical structure' entails (e.g., tree vs. nested format).

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?

No explicit guidance on when to use this tool versus alternatives like 'list_wiki_pages' or 'get_wiki_page'. The description implies usage for navigation, but doesn't specify contexts, prerequisites, or exclusions. This leaves the agent to infer based on tool names alone.

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