Skip to main content
Glama
Sign In
Azure DevOps Wiki MCP Server

Azure DevOps Wiki MCP Server

by uright
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

list_wiki

Lists all wikis in an Azure DevOps project, providing an overview of available documentation.

Instructions

List all wikis in a project

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": "list_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationNoAzure DevOps organization name
projectNoProject name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'list', implying read-only, but does not state idempotency, permission requirements, or behavior when project does not exist. This leaves ambiguity for the AI agent.

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 concise sentence that is front-loaded with key information. No unnecessary words, earning its place.

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 simplicity (list all wikis, two optional params, no output schema), the description is adequate but does not explain the effect of omitting parameters or the structure of the response, leaving some gaps.

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?

Both parameters (organization, project) have descriptions in the input schema, providing 100% coverage. The description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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 'List all wikis in a project' clearly states the action (list) and the resource (wikis) with a scope (in a project). It is distinct from siblings which focus on searching or individual page operations, though it does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives like search_wiki or wiki_get_page is provided. The context implies it is for retrieving all wikis, but lacks explicit context about when not to use it or prerequisites.

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

Deploy Server

Other Tools