Skip to main content
Glama

maket_page

Manage document pages: add, remove, rename, reorder, list, and set or read JSON Forms templates. Use it to organize page structure; edit content separately.

Instructions

When to use: manage page structure within a document — add, remove, rename, reorder, list. For page content, use maket_html instead.

Manage pages within a document. HTML can embed the current JSON Forms template at . add — append a page with html, json_forms, or both with one form slot; sets it active. remove — delete a page by 1-based index or name; refused if it's the last page. rename — rename a page by index or current name. reorder — move a page from one 1-based position to another; activePage adjusts. list — list pages with their template format; the active page is marked ●. set_form — replace the current form, preserving HTML with a form slot; without a slot, switch to a full-page form. get_form — read one page's JSON Forms template.

Note: charte compliance (token-literal colours, font-family, box-shadow) is enforced by maket_html set/patch, not by maket_page add. If the new page must match a charte, follow maket_page add with maket_html set to validate.

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": {
      "action": "<action>",
      "doc": "<doc>"
    },
    "name": "maket_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoFor reorder: target 1-based position.
docYesDocument name (always required).
fromNoFor reorder: source 1-based position.
htmlNoFor add: HTML body for the new page. Relative image src values are normalized to /assets/...
nameNoFor add/rename: page name (new page name, or rename target).
pageNoFor remove/rename: target page — either 1-based index or page name.
actionYesOperation to run. See the tool description for the action table.
json_formsNoFor add/set_form: JSON Forms template. Omit uischema to generate the form from the document-state JSON Schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / page / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / page / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed2 schema fields changedv2.2.0
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "add",
      -  "remove",
      -  "rename",
      -  "reorder",
      -  "list"
      -]New value: +[
      +  "add",
      +  "remove",
      +  "rename",
      +  "reorder",
      +  "list",
      +  "set_form",
      +  "get_form"
      +]
    • addedInput schema / properties / json_forms
      Added value: +{
      +  "description": "For add/set_form: JSON Forms template. Omit uischema to generate the form from the document-state JSON Schema.",
      +  "properties": {
      +    "uischema": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changedv1.7.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full safety burden and does well: it discloses that remove is refused for the last page, that add sets the page active, that reorder shifts activePage, and that charte validation is NOT performed here but by maket_html set/patch. It stops short of stating permissions, whether remove is destructive/undoable, or what the action responses look like.

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?

Front-loaded with usage guidance, then a scannable action list, then caveats. Slight redundancy in the transition from the 'When to use' line to 'Manage pages within a document', which largely restates it, but overall every block earns its place.

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 an 8-parameter tool with a nested json_forms object, no output schema, and no annotations, the description covers the action semantics, index base, active-page side effects, and the last-page guard. The main residual gap is the shape of returned data for list/get_form, which is only hinted at via the ● marker.

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 coverage is 100%, so the baseline is 3, but the action table adds cross-parameter meaning the schema lacks — which parameter applies to which action (page for remove/rename, from/to for reorder, 1-based numbering), plus the add/set_form distinction and the form-slot behavior. That is genuine value beyond the field-level descriptions.

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?

Opens with a specific verb set and resource: 'manage page structure within a document — add, remove, rename, reorder, list'. It also explicitly separates itself from the sibling that handles page content ('For page content, use maket_html instead'), so an agent can route without opening another schema.

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

Usage Guidelines5/5

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

The 'When to use' lead-in names the condition and the alternative for the adjacent case (maket_html for content). The per-action table tells the agent which action to pick for each intent, and the charte note tells it which tool actually enforces compliance.

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