Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

get_wiki_page

Retrieve wiki page content from Azure DevOps by specifying wiki ID and page path to access project documentation.

Instructions

Get the content of a wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdNoThe ID or name of the organization (Default: mycompany)
projectIdNoThe ID or name of the project (Default: MyProject)
wikiIdYesThe ID or name of the wiki
pagePathYesThe path of the page within the wiki

Implementation Reference

  • The core handler function that implements the logic to fetch and return the content of a specified wiki page using the Azure DevOps Wiki client.
    export async function getWikiPage(
      options: GetWikiPageOptions,
    ): Promise<string> {
      const { organizationId, projectId, wikiId, pagePath } = options;
    
      try {
        // Create the client
        const client = await azureDevOpsClient.getWikiClient({
          organizationId,
        });
    
        // Get the wiki page
        return (await client.getPage(projectId, wikiId, pagePath)).content;
      } catch (error) {
        // If it's already an AzureDevOpsError, rethrow it
        if (error instanceof AzureDevOpsError) {
          throw error;
        }
        // Otherwise wrap it in an AzureDevOpsError
        throw new AzureDevOpsError('Failed to get wiki page', { cause: error });
      }
    }
  • Zod schema defining the input parameters for the get_wiki_page tool, including organizationId, projectId, wikiId, and pagePath with descriptions and defaults.
    export const GetWikiPageSchema = z.object({
      organizationId: z
        .string()
        .optional()
        .nullable()
        .describe(`The ID or name of the organization (Default: ${defaultOrg})`),
      projectId: z
        .string()
        .optional()
        .nullable()
        .describe(`The ID or name of the project (Default: ${defaultProject})`),
      wikiId: z.string().describe('The ID or name of the wiki'),
      pagePath: z.string().describe('The path of the page within the wiki'),
    });
  • Registration of the get_wiki_page tool in the wikisTools array, specifying name, description, and input schema.
    {
      name: 'get_wiki_page',
      description: 'Get the content of a wiki page',
      inputSchema: zodToJsonSchema(GetWikiPageSchema),
    },
  • Handler case in handleWikisRequest that parses arguments with the schema and invokes the getWikiPage function for the 'get_wiki_page' tool name.
    case 'get_wiki_page': {
      const args = GetWikiPageSchema.parse(request.params.arguments);
      const result = await getWikiPage({
        organizationId: args.organizationId ?? defaultOrg,
        projectId: args.projectId ?? defaultProject,
        wikiId: args.wikiId,
        pagePath: args.pagePath,
      });
      return {
        content: [{ type: 'text', text: result }],
      };
    }
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 but offers minimal information. It doesn't mention whether this is a read-only operation, what authentication might be required, potential rate limits, error conditions, or what format the returned content will be in. 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 states the core purpose without unnecessary words. It's appropriately sized for a simple retrieval operation 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 format the wiki page content will be returned in (HTML, markdown, plain text), whether it includes metadata, or what happens if the page doesn't exist. The agent would need to guess about important behavioral aspects of this retrieval operation.

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?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for all four parameters. The baseline score of 3 reflects that the schema adequately documents parameters, but the description doesn't enhance understanding with additional context about parameter relationships or usage patterns.

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 ('Get') and resource ('content of a wiki page'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_wikis' or 'list_wiki_pages', which would require more specificity about what distinguishes this particular retrieval operation.

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 'search_wiki' or 'list_wiki_pages'. There's no mention of prerequisites, context, or exclusions that would help an agent choose appropriately among similar wiki-related tools.

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

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