Skip to main content
Glama
xrmghost

MCP Azure DevOps Server

by xrmghost
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_wiki_page_suggestions

Find wiki pages in Azure DevOps by typing partial titles or paths. This tool provides autocomplete suggestions to help users quickly locate documentation.

Instructions

Get page suggestions based on partial input - useful for autocomplete-like functionality.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.
partial_inputYesPartial page path or title to get suggestions for.

Implementation Reference

  • mcp_azure_devops/azure_devops_client.py:509-537 (handler)
    The core handler function that implements the get_wiki_page_suggestions tool logic. It fetches all wiki pages, scores them based on matching the partial_input, sorts by score, and returns the top 10 suggestions.
    def get_wiki_page_suggestions(self, project, wiki_identifier, partial_input):
    """
    Get page suggestions based on partial input.
    """
    pages = self.list_wiki_pages(project, wiki_identifier)
    suggestions = []
    
    for page in pages:
        path_lower = page["path"].lower()
        input_lower = partial_input.lower()
        
        # Score based on how well the input matches
        score = 0
        if path_lower.startswith(input_lower):
            score = 100  # Exact prefix match
        elif input_lower in path_lower:
            score = 50   # Contains match
        elif any(part.startswith(input_lower) for part in path_lower.split("/")):
            score = 25   # Part starts with input
        
        if score > 0:
            suggestions.append({
                **page,
                "match_score": score
            })
    
    # Sort by score and return top suggestions
    suggestions.sort(key=lambda x: x["match_score"], reverse=True)
    return suggestions[:10]
  • mcp_azure_devops/server.py:763-785 (registration)
    Registers the get_wiki_page_suggestions tool in the MCP server, including its name, description, and input schema definition.
    types.Tool(
    name="get_wiki_page_suggestions",
    description="Get page suggestions based on partial input - useful for autocomplete-like functionality.",
    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."
            },
            "partial_input": {
                "type": "string", 
                "description": "Partial page path or title to get suggestions for."
            },
        },
        "required": ["project", "wiki_identifier", "partial_input"],
        "additionalProperties": False
    }
),
  • mcp_azure_devops/server.py:766-785 (schema)
    Defines the input schema for the get_wiki_page_suggestions tool, specifying parameters project, wiki_identifier, and partial_input.
        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."
            },
            "partial_input": {
                "type": "string", 
                "description": "Partial page path or title to get suggestions for."
            },
        },
        "required": ["project", "wiki_identifier", "partial_input"],
        "additionalProperties": False
    }
),
  • mcp_azure_devops/server.py:1041-1042 (helper)
    Dispatch handler in the server's _execute_tool method that calls the client implementation for get_wiki_page_suggestions.
    elif name == "get_wiki_page_suggestions":
    return self.client.get_wiki_page_suggestions(**arguments)

Tool Definition Quality

B3.3/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 burden of behavioral disclosure. It mentions the tool is 'useful for autocomplete-like functionality', which hints at a read-only, non-destructive operation, but doesn't explicitly state safety, permissions, rate limits, or what the return format looks like. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose and adds a brief usage note. Every word earns its place with zero waste, making it appropriately sized and easy to parse.

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 the tool's moderate complexity (3 required parameters) and no annotations or output schema, the description is adequate but incomplete. It covers the basic purpose and usage hint, but lacks details on behavioral traits, return values, or error handling, which are needed for full contextual understanding.

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, partial_input) with clear descriptions. The description adds minimal value beyond the schema by implying 'partial_input' is used for suggestions, but doesn't provide additional syntax, format details, or examples. Baseline 3 is appropriate when 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 tool's purpose: 'Get page suggestions based on partial input' with the specific verb 'Get' and resource 'page suggestions'. It distinguishes from siblings like 'get_wiki_page' or 'search_wiki_pages' by focusing on autocomplete functionality, though it doesn't explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context with 'useful for autocomplete-like functionality', suggesting when to use this tool. However, it doesn't provide explicit guidance on when to choose this over similar tools like 'search_wiki_pages' or 'get_recent_wiki_pages', nor does it mention any exclusions or prerequisites.

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