Skip to main content
Glama

ZeroWidth

by ai.zerowidth
OverviewDiscussionsAdmin

Edit a Napkin diagram

napkin_diagrams_update
Destructive

Edit a Napkin diagram: retitle, describe, REPLACE the whole mermaid source, set visibility, or archived (true takes it out of the gallery, false brings it back — the recovery move for a diagram created by mistake). Read the diagram first (napkin_diagrams_get) so your new source keeps the parts the user wants. Diagram ids come from napkin_diagrams_list.

Input Schema

NameRequiredDescriptionDefault
titleNo
sourceNoMermaid flowchart source. Start with `flowchart TD` (top-down) or `flowchart LR` (left-right). Declare shaped nodes — `A["Rect"]`, `B("Rounded")`, `C{"Decision"}`, `D(["Stadium"])`, `E(("Circle"))`, `F{{"Hexagon"}}` — and link them with `A -->|label| B`, `A -.-> B` (dotted), or `A ==> B` (thick). Group steps with `subgraph Name["Title"] ... end`. Color a node with a trailing `style A fill:#fee2e2` line. Only the flowchart subset is supported. Each label is a short name on one line, written plainly: no `\n`, no backslashes before quotes. A step's label is its name everywhere in Compass.
archivedNo
diagramIdYesDiagram id from napkin_diagrams_list.
workspaceNoWorkspace slug. Personal tokens with no default workspace MUST pass this; tokens with a default can override per call. Ignored for workspace API keys.
approvalIdNoApproval id from a prior needs_confirmation response. Omit on the first call.
visibilityNoWho can see it: PRIVATE (only the user), WORKSPACE (every member, the default), or SHARED (specific people, granted afterwards). Say 'make it private' → PRIVATE.
descriptionNoShort gallery summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Mermaid flowchart source. Start with `flowchart TD` (top-down) or `flowchart LR` (left-right). Declare shaped nodes — `A[\"Rect\"]`, `B(\"Rounded\")`, `C{\"Decision\"}`, `D([\"Stadium\"])`, `E((\"Circle\"))`, `F{{\"Hexagon\"}}` — and link them with `A -->|label| B`, `A -.-> B` (dotted), or `A ==> B` (thick). Group steps with `subgraph Name[\"Title\"] ... end`. Color a node with a trailing `style A fill:#fee2e2` line. Only the flowchart subset is supported."New value: +"Mermaid flowchart source. Start with `flowchart TD` (top-down) or `flowchart LR` (left-right). Declare shaped nodes — `A[\"Rect\"]`, `B(\"Rounded\")`, `C{\"Decision\"}`, `D([\"Stadium\"])`, `E((\"Circle\"))`, `F{{\"Hexagon\"}}` — and link them with `A -->|label| B`, `A -.-> B` (dotted), or `A ==> B` (thick). Group steps with `subgraph Name[\"Title\"] ... end`. Color a node with a trailing `style A fill:#fee2e2` line. Only the flowchart subset is supported. Each label is a short name on one line, written plainly: no `\\n`, no backslashes before quotes. A step's label is its name everywhere in Compass."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description reinforces this by emphasizing that source REPLACE-es the whole mermaid source, plus explains archived semantics (removes/restores from gallery). It discloses what is overwritten and a recovery path, adding real context beyond the annotations, though it does not describe auth or approval flow.

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 the core verb and effects, then the read-first workflow, then the id source. Dense but every clause carries actionable information; the archived parenthetical earns its length by explaining recovery semantics.

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-param destructive mutation with no output schema, it covers what can change, the read-before-write prerequisite, id sourcing, and the archive recovery path. Approval/workspace mechanics are left to the schema descriptions, which is acceptable, so nothing an agent needs is 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?

With schema coverage at 75% the baseline is 3, and the description earns above that: it maps each mutable operation to a field (retitle→title, describe→description, source replacement, visibility) and adds the crucial 'whole source is replaced' semantics and archived recovery behavior that the bare enum/boolean schema does not convey.

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?

States a specific verb (edit) and resource (Napkin diagram) and enumerates the exact mutable fields (title, description, mermaid source, visibility, archived). This clearly separates it from napkin_diagrams_create, napkin_diagrams_get and napkin_diagrams_list without the agent opening any schema.

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?

Gives a concrete workflow: read via napkin_diagrams_get first so the new source preserves wanted parts, and get ids from napkin_diagrams_list. It also frames archived=false as the recovery move for a mistaken diagram. It stops short of explicit when-not/alternatives routing, but the prerequisite guidance is strong.

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

All ZeroWidth toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources