Skip to main content
Glama

refactor-notes

Restructure your notes by splitting at specified headings, merging multiple notes into one, or extracting sections into new notes to improve organization and clarity.

Instructions

Unified tool for structural note refactoring: split notes by heading, merge multiple notes, and extract sections to new notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'split', 'merge', 'extract-section'
pathNoSource note path
levelNoHeading level to split at (default: 2, for split action)
keep_originalNoKeep extracted content in original note (for split action)
output_dirNoDirectory for new notes (for split action)
dry_runNoPreview changes without modifying files
pathsNoComma-separated list of notes to merge (for merge action)
outputNoOutput note path
separatorNoSeparator between notes (for merge action)
delete_originalsNoDelete original notes after merge (for merge action)
add_headingsNoAdd note names as headings (for merge action)
headingNoHeading to extract (for extract-section action)
remove_from_originalNoRemove from source note (default true, for extract-section action)
add_linkNoAdd link to new note in source (default true, for extract-section action)
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It omits details about file modifications, destructiveness, or side effects. The dry_run parameter hints at changes but is not described in prose. For a mutation tool, this is insufficient.

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?

The description is a single sentence that efficiently captures the tool's purpose. No redundant or extraneous content. Front-loaded with key actions.

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?

Given the high parameter count (14) and lack of output schema, the description is minimally complete. It explains the three actions but lacks workflow context, examples, or tie-in to other tools. Adequate but not enriched.

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% (all 14 parameters have descriptions). The tool description adds no extra meaning beyond the schema; it merely lists actions. Baseline 3 is appropriate as the schema already does heavy lifting.

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?

The description clearly states the tool performs three specific structural refactoring actions: split, merge, and extract-section. It effectively distinguishes from sibling tools like 'edit-note' or 'manage-notes' by specifying the unified refactoring purpose.

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?

The description implies usage for structural refactoring but does not explicitly state when to use this tool versus alternatives like 'edit-note' or 'bulk-operations'. No guidance on when not to use or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zach-snell/obx'

If you have feedback or need assistance with the MCP directory API, please join our Discord server