Skip to main content
Glama
stefanskiasan

Azure DevOps MCP Server for Cline

get_wiki_page

Retrieve Azure DevOps wiki pages by specifying the wiki identifier and page path to access documentation or content stored in the wiki.

Instructions

Get a wiki page by path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wikiIdentifierYesWiki identifier
pathYesPage path
versionNoVersion (optional, defaults to main)
includeContentNoInclude page content (optional, defaults to true)

Implementation Reference

  • The primary handler function implementing the get_wiki_page tool logic. It validates input arguments, initializes the Azure DevOps connection, fetches wiki information using WikiApi, and returns a formatted MCP response (noting current limitation on page content).
    export async function getWikiPage(args: GetWikiPageArgs, config: AzureDevOpsConfig) {
      if (!args.wikiIdentifier || !args.path) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Wiki identifier and page path are required'
        );
      }
    
      AzureDevOpsConnection.initialize(config);
      const connection = AzureDevOpsConnection.getInstance();
      const wikiApi = await connection.getWikiApi();
    
      try {
        // Get wiki information
        const wiki = await wikiApi.getWiki(config.project, args.wikiIdentifier);
        if (!wiki || !wiki.id) {
          throw new McpError(
            ErrorCode.InvalidParams,
            `Wiki ${args.wikiIdentifier} not found`
          );
        }
    
        // For now, we can only return the wiki information since the page API is not available
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                id: wiki.id,
                name: wiki.name,
                path: args.path,
                message: 'Wiki page content retrieval is not supported in the current API version'
              }, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        if (error instanceof McpError) throw error;
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to get wiki page: ${errorMessage}`
        );
      }
    }
  • The input schema definition for the get_wiki_page tool, specifying properties, descriptions, and required fields.
    name: 'get_wiki_page',
    description: 'Get a wiki page by path',
    inputSchema: {
      type: 'object',
      properties: {
        wikiIdentifier: {
          type: 'string',
          description: 'Wiki identifier',
        },
        path: {
          type: 'string',
          description: 'Page path',
        },
        version: {
          type: 'string',
          description: 'Version (optional, defaults to main)',
        },
        includeContent: {
          type: 'boolean',
          description: 'Include page content (optional, defaults to true)',
        },
      },
      required: ['wikiIdentifier', 'path'],
    },
  • TypeScript interface defining the arguments for the getWikiPage handler function.
    interface GetWikiPageArgs {
      wikiIdentifier: string;
      path: string;
      version?: string;
      includeContent?: boolean;
    }
  • Wrapper function in wikiTools.initialize that binds the getWikiPage handler with config for tool invocation.
    getWikiPage: (args: { wikiIdentifier: string; path: string; version?: string; includeContent?: boolean }) =>
      getWikiPage(args, config),
  • src/index.ts:142-143 (registration)
    Dispatch logic in the main MCP server that routes 'get_wiki_page' tool calls to the wiki tools instance.
    case 'get_wiki_page':
      result = await tools.wiki.getWikiPage(request.params.arguments);
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. 'Get a wiki page by path' implies a read-only operation, but it doesn't disclose any behavioral traits such as authentication requirements, rate limits, error handling, or what happens if the page doesn't exist. The description is minimal and lacks critical context for safe and effective use.

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 'Get a wiki page by path' is a single, efficient sentence that front-loads the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool, with zero waste or redundancy, making it easy to parse quickly.

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 tool with 4 parameters and read operations. It doesn't explain return values, error cases, or behavioral constraints, leaving significant gaps. For a get operation, more context on what 'Get' entails (e.g., content format, permissions) is needed to be fully helpful.

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 all parameters documented in the schema (wikiIdentifier, path, version, includeContent). The description adds no meaning beyond the schema—it doesn't explain parameter relationships, format examples, or usage nuances. Baseline is 3 since the schema does the heavy lifting, but the description doesn't compensate with additional insights.

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 'Get a wiki page by path' clearly states the verb 'Get' and resource 'wiki page', with the method 'by path' providing specific retrieval mechanism. It distinguishes from siblings like 'get_wikis' (list wikis) and 'update_wiki_page' (modify), though not explicitly named. However, it doesn't fully differentiate from 'get_work_item' or other get_* tools in purpose beyond the resource type.

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. It doesn't mention when to choose this over 'get_wikis' (for listing wikis) or 'update_wiki_page' (for modifications), nor does it specify prerequisites like needing a wiki identifier. Usage is implied only by the tool name and description, with no explicit context or exclusions provided.

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

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