arcade-azure-devops-mcp

AzureDevops_ListWikis

AzureDevops_ListWikis

List all wikis in an Azure DevOps project or organization to quickly locate documentation repositories.

Instructions

List wikis in a project or organization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "AzureDevops_ListWikis"
  }
}

Input Schema

Name	Required	Description	Default
`project`	No	Project name or ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. It discloses the scope (project or organization), but omits behavioral details like what happens when 'project' is omitted (does it default to organization?), the shape of the returned data, or pagination. For a read-only list operation, this is adequate but minimal.

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, short sentence with a front-loaded verb and no redundant words. It is appropriately concise for the tool's simplicity.

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

Completeness4/5

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

The tool is simple (one optional parameter, no output schema), and the description gives the essential purpose and scope. However, it could clarify the behavior when 'project' is absent and mention the return type, but these gaps are minor for a list 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 schema description covers 100% with 'Project name or ID (optional)'. The tool description adds the 'organization' dimension, hinting at alternate behavior, but does not explain how the parameter selects between project- and organization-level listing beyond the schema's own text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'List' with a clear resource 'wikis' and scope 'project or organization'. It distinguishes from sibling tools like AzureDevops_GetWikiPage, which fetches a single page, and other list tools for different resources.

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 guidance is given on when to use this tool versus alternatives. It doesn't mention when to prefer it over GetWikiPage or other list tools, nor any exclusions or prerequisites. The agent is left to infer usage from the action alone.

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