Skip to main content
Glama

maket_reader

Render a Maket document page without image data, retrieve a page image downscaled to its displayed width, or write a value into a state document to update reader-view forms.

Instructions

Calls of the Maket reader view (ui://maket/page): page returns one rendered page without image data, image returns one of its images downscaled to the displayed width, write sets one value of a state document as the Maket form does. Not for agents.

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_reader"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNoFor write: patch op.
docYesDocument name.
fileNoFor image: the asset file, one of the page's images.
pageNoFor page and image: 1-based page number.
pathNoFor write: JSON Pointer of the value.
valueNoFor write: the new value.
widthNoFor image: displayed width in device pixels.
actionYespage, image or write.
expectedRevisionNoFor write: the state revision the value was edited from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / value / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / value / type
      Added value: +[
      +  "string",
      +  "number",
      +  "boolean",
      +  "null"
      +]
  2. Addedv2.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full safety burden. It usefully states that page omits image data, image is downscaled to display width, and write mutates one state value, but it omits write side effects, concurrency behavior via expectedRevision, permissions, and reversibility.

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 definition is a single compact sentence that front-loads the reader-view context and uses a colon to list actions. It is somewhat run-on and buries the important 'Not for agents' clause at the end, but it has little wasted text.

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?

For a multi-action tool with a mutating write path, no annotations, no output schema, and nine parameters, the description covers action returns but leaves out mutation safety, concurrency, and error behavior. It does describe the return shape for page and image, which prevents a lower score.

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 coverage is 100%, so the schema already defines all nine parameters and enum values. The description adds plain-language meaning for the action outcomes but does not explain parameters like expectedRevision or doc beyond the schema, so it meets the baseline.

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 the Maket reader view and enumerates its three actions (page, image, write) with concrete outcomes, so the agent can tell what the tool does. It does not explicitly differentiate itself from siblings such as maket_page or maket_state, which keeps it from a 5.

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?

The only selection guidance is 'Not for agents,' which is a blanket exclusion rather than a when-to-use rule, and no alternative sibling is named. An agent gets no positive condition for choosing this tool over maket_page, maket_state, or maket_image.

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