arcade-azure-devops-mcp

AzureDevops_GetWikiPage

AzureDevops_GetWikiPage

Retrieve a specific Azure DevOps wiki page by project, wiki identifier, and path. Optionally include its content for direct access.

Instructions

Get a specific wiki page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "wiki_identifier": "<wiki_identifier>",
      "path": "<path>"
    },
    "name": "AzureDevops_GetWikiPage"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Page path (e.g., '/Home')
`project`	Yes	Project name or ID
`include_content`	No	Include page content in response
`wiki_identifier`	Yes	Wiki name or ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

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 the full burden of behavioral disclosure. It only states 'Get a specific wiki page' and does not mention the include_content parameter, return format, error behavior, or any operational side effects. This is insufficient for a tool with no annotation support.

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 sentence, front-loaded with the action and resource, containing zero fluff. It is concise and to the point, which is appropriately sized for a simple GET operation.

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 the lack of annotations and output schema, this description is too sparse. It does not explain what the response contains, the role of the include_content flag, or any constraints on the path. For a tool with 4 parameters and no structured output schema, the description is inadequate for the agent to fully understand the tool's behavior.

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 input schema already provides complete parameter descriptions (100% coverage), so the baseline is 3. The description adds no additional meaning about parameters or their semantics; it simply restates the general purpose without enriching the meaning of path, project, wiki_identifier, or include_content.

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 ('specific wiki page'), making it easy to identify what the tool does. However, it does not explicitly differentiate from sibling tools like AzureDevops_ListWikis, and lacks additional scope details such as the required project/wiki/path parameters.

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, prerequisites, or exclusions. There is no mention of when to use this over other wiki-related tools, leaving the agent without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.