Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Update wiki page

devops_wiki_page_update
Destructive

Updates an existing wiki page in an on-premises Azure DevOps wiki by wiki and page ID, with optional new content.

Instructions

Update an existing 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": {
      "wiki_id": "<wiki_id>",
      "page_id": "<page_id>"
    },
    "name": "devops_wiki_page_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentNoNew content for the wiki page (optional).
page_idYesWiki page ID.
wiki_idYesWiki identifier (name or ID).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedInput schema / properties / organization
      Removed value: -{
      -  "description": "DevOps organization name.",
      -  "type": "string"
      -}
    • removedInput schema / properties / project
      Removed value: -{
      -  "description": "DevOps project name.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "organization",
      -  "project",
      -  "wiki_id",
      -  "page_id"
      -]New value: +[
      +  "wiki_id",
      +  "page_id"
      +]
  2. First observedv0.3.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the supplied content replaces all existing page content, whether other fields are preserved, or what authorization is needed for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no padding and the scope stated up front, so nothing is wasted. However, its brevity reflects under-specification rather than efficiency; it conveys essentially the same information as the title.

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?

This is a destructive write tool where the key agent questions are what gets overwritten and how it differs from create_or_update; neither is answered. The existence of an output schema excuses it from describing return values, but the mutation semantics and sibling routing remain undocumented.

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 each of the three parameters documented in the schema, so the baseline is 3. The description contributes no additional meaning about content semantics (full replacement vs. append) or accepted wiki_id forms beyond what the schema already states.

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

Purpose2/5

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

"Update an existing wiki page" restates the tool name and title almost verbatim, adding only the word "existing." It does not distinguish this tool from the sibling devops_wiki_page_create_or_update, which by its name covers overlapping behavior, so an agent cannot tell from the description which one to pick.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as page existence or permissions, and no explicit alternative named. The implied context is mutation of an existing page, but the agent must infer that entirely.

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