Skip to main content
Glama

write_ensure_path

Ensure a wiki page path exists by creating every missing segment and assigning the title and kind to the final segment.

Instructions

Make sure a path exists, creating every missing segment; the last one gets the title.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOf the last segment; section: a folder-like page for children
pathYes
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already carry the safety profile (destructiveHint=false, openWorldHint=false), and the description adds real behavioral detail: intermediate segments are created rather than failing the call. It leaves one important gap, namely whether an already-existing last segment is retitled, left alone, or errors.

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

Conciseness5/5

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

A single dense sentence with zero waste; the creation semantics are front-loaded before the title-placement rule.

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 three-parameter mutation tool with no output schema, the definition conveys the core contract (create missing segments, title the last segment) and is backed by annotations for the safety profile. The unresolved case of an existing terminal segment is the only material omission.

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 only 33%, with just `kind` documented, so the description must compensate. It partially does by explaining the path is a hierarchy of segments and that the title is applied to the last segment, but it says nothing about path syntax or title constraints.

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 concrete verb plus resource: ensure a path exists, creating every missing segment. That distinguishes it from a plain page-creation tool because it operates on a whole path hierarchy. It does not explicitly name write_create_page as the contrasting sibling, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'Make sure a path exists', which suggests idempotent create-if-missing semantics, and the agent must infer this is preferable to write_create_page when intermediate segments may be absent. There is no explicit when-to-use or when-not condition.

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