Skip to main content
Glama

write_append

Append Markdown to the end of a LeafWiki page by page ID or path, enabling ordered content additions without overwriting existing text.

Instructions

Add Markdown at the end of a 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": {
      "page": "<page>",
      "text": "<text>"
    },
    "name": "write_append"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is partly covered. The description usefully clarifies that content is added at the end, implying existing content is preserved, but says nothing about whether a missing page is created, how newlines or separators are handled, or what the call returns.

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?

One short sentence with the key constraint ('at the end') front-loaded and no filler. It is efficient, though lean enough that a slight expansion of the append semantics would not have hurt readability.

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?

For a simple two-parameter mutation with no output schema, the description covers the core action but leaves notable gaps: return value, behavior on a nonexistent page, and how it differs from other write tools. The annotation set is thin (no readOnlyHint), so the description should carry more of the behavioral burden.

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 coverage is 50%: the `page` parameter is documented as 'Page id or path,' while `text` has no schema description. The description compensates partially by specifying that the appended text is Markdown, which is real meaning beyond the schema, but it does not clarify whether `page` accepts a bare title or whether `text` must be non-empty Markdown fragment.

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 names a specific verb and resource: adding Markdown to the end of an existing page. It is clearly an additive write, but it does not distinguish itself from close siblings like write_edit_text or write_update_page, so an agent must infer the boundary.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'at the end' implies append semantics versus a general edit, but nothing names the alternative tool to use for modifying existing content or for prepending.

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