Skip to main content
Glama

write_create_page

Create a page or section under a parent, with optional Markdown content, tags, and properties to organize LeafWiki documentation.

Instructions

Create a page (or section) under a parent, optionally with content, tags and properties.

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": {
      "title": "<title>"
    },
    "name": "write_create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNosection: a folder-like page for children
slugNoURL segment; omit to derive it from the title
tagsNoFull tag list, replaces the current one
titleYes
parentNoParent id or path; omit for the top level
contentNoMarkdown; default "# Title"
propertiesNoFull property map, replaces the current one

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 agent knows this is a contained, non-destructive mutation. The description adds little beyond restating the optional payload fields; it says nothing about slug/title collisions, whether creation fails when a page already exists at that path, or required permissions — significant unknowns for a create operation.

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 front-loaded sentence with the action and resource first and qualifiers after; nothing is wasted. The trailing 'optionally with content, tags and properties' is slightly redundant with the schema but is short enough not to hurt.

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 7-parameter write tool with a nested object and no output schema, the description covers the happy path but omits collision/failure behavior and what is returned on success. It is adequate rather than complete.

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 86%, so the schema already documents kind, slug, tags, parent, content and properties, including the 'replaces the current one' semantics. The description's 'optionally with content, tags and properties' only restates optionality and adds no format or behavior detail beyond the schema; the baseline 3 applies.

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 gives a specific verb ('Create') and resource ('a page (or section)'), plus the scoping condition 'under a parent'. That clearly separates it from write_update_page / write_move in the sibling list, though it never names an alternative explicitly.

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 statement of when to use this versus write_update_page (existing page) or write_ensure_path (create-if-missing), and no preconditions are given. The only implied guidance is 'under a parent', which the schema already covers more precisely.

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