Skip to main content
Glama

write_sort

Set the order of a page's children by passing the parent ID or path and the child IDs or paths in the new sequence. Use it to reorder nested pages in LeafWiki.

Instructions

Set the order of the children 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": {
      "parent": "<parent>",
      "order": "<order>"
    },
    "name": "write_sort"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesEvery child id or path, in the new order
parentYesParent id or path; "/" for the top level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations only declare openWorldHint=false and destructiveHint=false, leaving the mutation itself undocumented. The one-line description does not say whether omitting a child drops it from the tree, whether the call is idempotent, what permissions it needs, or why destructiveHint is false when it rewrites ordering. It adds nothing beyond the read-write safety hints.

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?

The single sentence is front-loaded and has no waste. At the same time, the brevity looks more like under-specification than discipline for a write tool that rewrites a whole ordering.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter write tool with no output schema and no readOnlyHint, the definition should explain what an ordering call does to the children it does not mention and what the result confirms. It does not, so an agent has to discover the semantics by trial and error.

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%, with both order and parent documented clearly, including that order must contain every child and that "/" means top level. The description adds no meaning beyond what the schema already provides, so the baseline 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 names a specific verb and resource: set the order of a page's children. That is enough for an agent to distinguish reordering from siblings like write_move or write_append, though it never states how it differs from write_move, which could also change a child's position.

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 guidance, no prerequisites and no named alternatives. The agent must infer that this tool rewrites the entire ordering rather than moving one child, and that write_move is the tool for a single move.

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