Skip to main content
Glama
MCP Agent Operations

MCP Agent Operations

render_hierarchy_html

Render inline mappings, sequences, JSON, or YAML into safe self-contained hierarchy HTML without filesystem access, and optionally write the output to an authorized absolute folder.

Instructions

Render safe self-contained hierarchy HTML and optionally save it.

Inline mappings, sequences, JSON, and YAML require no filesystem access. An explicit source path, custom theme folder, or output folder must be absolute and resolve beneath the hierarchy roots. A filename without an explicit or configured output folder returns inline HTML without writing a file.

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>"
    },
    "name": "render_hierarchy_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNoPackaged or custom theme base name without `.css`.default
titleNoBrowser and page title.Hierarchy
sourceYesInline mapping, sequence, JSON, YAML, or an absolute JSON/YAML path.
numberingNoAdd one-based dotted hierarchy numbers.
checkboxesNoAdd read-only completion markers.
output_folderNoOptional absolute destination beneath an authorized hierarchy root.
themes_folderNoAbsolute folder for a custom theme, or null for packaged themes.
completed_itemsNoExact dotted paths rendered as complete; requires checkboxes.
output_filenameNoOptional base HTML filename without a directory.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • changedInput schema / properties / output_folder / description
      Previous value: -"Optional absolute destination beneath a configured workspace."New value: +"Optional absolute destination beneath an authorized hierarchy root."
  2. Addedv0.11.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the essential traits: output is self-contained HTML, inline sources touch no filesystem, and writes only occur when an output folder is supplied and within authorized roots. That is meaningful side-effect disclosure for a tool that can persist files. It does not address overwrite/conflict behavior for an existing filename or any permission failures, which are the remaining behavioral unknowns.

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?

Three tight sentences with the core action front-loaded and the constraint and fallback rules following in logical order. Every sentence carries information; the middle sentence is dense but its absolute-path and root-confinement rules both matter. Minor cost: the source-type list is split awkwardly across the first two sentences.

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

Completeness5/5

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

With 9 parameters, no annotations, and an output schema covering return values, the description supplies exactly what structured fields can't: which source forms avoid the filesystem, what path rules apply, and what determines whether a file is written. Nothing an agent needs before a correct first call appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, and the description adds real meaning on top by tying `output_folder`/`output_filename` absence to the no-write inline return, and by tying source forms to filesystem requirements. It doesn't clarify interactions among parameters, notably that `completed_items` depends on `checkboxes` (that constraint lives only in the schema) or how `theme` interacts with `themes_folder`.

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?

"Render safe self-contained hierarchy HTML and optionally save it" gives a concrete verb plus resource, and the following sentence enumerates the accepted source forms (inline mapping, sequence, JSON, YAML, or an absolute path). What it doesn't do is name any sibling or boundary, so an agent must infer from the tool name alone that this is the only rendering path among the plan/claim/skill/reference tools.

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

Usage Guidelines4/5

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

It gives clear operating context: inline inputs need no filesystem access, while a source path, theme folder, or output folder must be absolute and resolve beneath the hierarchy roots. The decisive guidance — omitting an output folder (explicit or configured) yields inline HTML with no file written — tells the agent exactly how to get non-writing versus writing behavior. It stops short of stating exclusions or when to prefer a sibling, but the write/no-write rule covers the main branch point.

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