Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Create or update wiki page

devops_wiki_page_create_or_update
Destructive

Creates or updates a wiki page under a specified parent path and updates the existing page when the title matches.

Instructions

Create or update a wiki page under the specified parent 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>",
      "parent_path": "<parent_path>",
      "title": "<title>"
    },
    "name": "devops_wiki_page_create_or_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the new wiki page. If a page with the same title already exists under the parent, it will be updated.
contentNo
wiki_idYesWiki identifier (name or ID).
parent_pathYesRelative path of the parent wiki page, or '/' for root.

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",
      -  "parent_path",
      -  "title"
      -]New value: +[
      +  "wiki_id",
      +  "parent_path",
      +  "title"
      +]
  2. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/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 bar is lower, but the single most important behavior is undisclosed: this tool silently overwrites an existing page when the title matches, and 'content' defaults to an empty string. That means a create call with a colliding title can blank a live wiki page, which the description never warns about. With destructiveHint already flagged, this adds partial value but leaves the core risk implicit.

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

Conciseness4/5

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

A single tight sentence with no filler, and the resource is front-loaded. It is efficiently sized for the message it carries, though that economy comes at the cost of the behavioral detail the tool actually needs.

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?

With annotations covering the safety profile and an output schema handling return values, the description need not restate those. What remains missing is the destructive upsert semantic, which is nonetheless recoverable from the title parameter's schema description. Adequate overall, with a small gap on the overwrite risk.

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 75%, so the schema largely documents the four parameters, including the crucial 'same title means update' note on title and the '/' root convention on parent_path. The description contributes nothing parameter-specific beyond 'specified parent page', so baseline 3 applies. It could have clarified that omitting content on an update empties the page.

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 states a specific verb pair and resource: 'Create or update a wiki page under the specified parent page.' That is clear enough to act on, but it never distinguishes this upsert from the sibling 'devops_wiki_page_update', which is exactly the ambiguity an agent needs resolved. The upsert trigger (same title under the parent) lives only in the schema, not here.

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 at all, and no mention of the closely named 'devops_wiki_page_update' sibling. An agent cannot tell from this description whether to prefer this tool or the dedicated update tool for editing an existing page. The phrase 'under the specified parent page' hints at scope but is not routing guidance.

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