create_hierarchy_plan
Create a hierarchy plan from inline structured data or JSON/YAML files, saving durable HTML/JSON outputs or returning canonical inline JSON when no destination is set.
Instructions
Create a hierarchy plan as durable files or canonical inline JSON.
Source, theme, and output paths must be absolute beneath the hierarchy roots. The
output folder defaults to MCP_AGENT_OPS_HIERARCHY_OUTPUT_FOLDER. When neither
destination is supplied, the tool returns JSON without writing files.
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": {
"source": "<source>",
"output_filename": "<output_filename>"
},
"name": "create_hierarchy_plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| theme | No | Packaged or custom theme base name without `.css`. | default |
| title | No | Browser and page title. | Hierarchy plan |
| source | Yes | Inline mapping, sequence, JSON, YAML, or an absolute JSON/YAML path. | |
| output_folder | No | Optional absolute destination beneath an authorized hierarchy root. Overrides the configured default folder. | |
| themes_folder | No | Absolute folder for a custom theme, or null for packaged themes. | |
| completed_items | No | Exact dotted paths or unique titles initially marked complete. | |
| output_filename | Yes | Base HTML filename; the JSON plan uses the same base name. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |