Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Append content to Wiki page

wiki_pages_append

Append a YFM fragment to a wiki page without rewriting its full body; insert content at the top, bottom, a numbered section, or a named anchor, then return the updated page.

Instructions

Append a YFM fragment to a wiki page without rewriting the whole body.

Unlike pages_update (full replace), this adds body.content at the chosen spot: body.body.location (top/bottom of the page), a numbered body.section, or a named text body.anchor. Returns the updated page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesWhat to append and where: required ``content`` (YFM fragment) plus optional ``body`` (top/bottom), ``section`` or ``anchor`` placement.
fieldsNoExtra blocks to include in the reply (CSV), e.g. ``content,attributes``.
page_idYesNumeric id of the page to append to.
is_silentNoDo not notify the page's subscribers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.122.1
    • changedInput schema / properties / body / properties / anchor / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "Append relative to a named text anchor (``append-content`` ``anchor``).",
-    "properties": {
-      "fallback": {
-        "default": false,
-        "description": "Fall back to the body end if the anchor is not found.",
-        "type": "boolean"
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Anchor text to append next to."
-      },
-      "regex": {
-        "default": false,
-        "description": "Treat ``name`` as a regular expression.",
-        "type": "boolean"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "description": "Append relative to a named text anchor (``append-content`` ``anchor``).",
+    "properties": {
+      "fallback": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Fall back to the body end if the anchor is not found."
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Anchor text to append next to."
+      },
+      "regex": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Treat ``name`` as a regular expression."
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / is_silent / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / is_silent / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / is_silent / type
      Removed value: -"boolean"
  2. First observedv0.67.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is partly covered. The description still adds real value beyond them: it clarifies the operation does not rewrite the whole body, and that it returns the updated page. It does not discuss idempotency or the silent-notification behavior, which stays in the schema.

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?

Three tight sentences that front-load the core action and the sibling contrast before detailing placement. The RST-style double backticks add mild visual noise but no filler; every sentence carries information.

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?

For a nested-object mutation tool, the description covers the action, the placement variants, and the return value ('Returns the updated page'), even without an output schema. Secondary parameters like fields and is_silent are documented in the schema, so nothing critical is missing.

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% and the nested body structure (location/section/anchor/content) is fully documented in the schema itself. The description mirrors those concepts ('top/bottom of the page', 'a numbered body.section', 'a named text anchor') without adding syntax or constraints beyond the schema, so the baseline 3 applies.

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?

States a specific verb (append) and resource (wiki page) with the exact scope ('a YFM fragment') and immediately contrasts it with the closest sibling, pages_update, as a full replace. An agent can distinguish this from every other wiki_* tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative tool (pages_update) and the reason to prefer this one (partial edit rather than full body rewrite), and enumerates the three placement modes. It stops short of stating explicit exclusions (e.g. when appending is inappropriate vs updating), so it lands just under a full 5.

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