Skip to main content
Glama
yenchieh

DiagramZu

by yenchieh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_deck

Update a DiagramZu deck's title, description, and slide order by passing the complete ordered list of diagram IDs. Reordering, adding, or removing slides is done by sending the new full list.

Instructions

Update a deck's title, description, and/or slide order. slides is DECLARATIVE: pass the complete desired ordered list of diagram ids — reorder, add, and remove are all expressed by sending the new full list (any id omitted is removed from the deck; new ids are appended in the order given). Returns the deck id and the present URL, which only members of this Space can open — it is NOT a shareable link. To share the deck outside the Space, someone in the Space opens it in DiagramZu and uses its Share button, which mints a public read-only link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDeck UUID
spaceNoWhich workspace to act in: its id, its slug, or its exact name (case-insensitive). Omit to use this token's default workspace. Call list_spaces to see what this token can reach. A name that matches more than one workspace is refused — pass the id or slug instead.
titleNoDeck title shown in the deck list and above the presentation (≤200 chars).
slidesNoComplete ordered list of diagram UUIDs that should be in the deck after this update. Omit to leave the slides unchanged; pass [] to clear all slides.
descriptionNoOne-line summary of what the deck covers (≤1000 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.7
    • addedInput schema / properties / space
      Added value: +{
+  "description": "Which workspace to act in: its id, its slug, or its exact name (case-insensitive). Omit to use this token's default workspace. Call list_spaces to see what this token can reach. A name that matches more than one workspace is refused — pass the id or slug instead.",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.0.6
    • changedInput schema / properties / title / description
      Previous value: -"Deck title shown in the deck list and above the presentation."New value: +"Deck title shown in the deck list and above the presentation (≤200 chars)."
  3. Addedv0.0.4

TDQS

A4.1/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 burden and does well: it discloses the destructive/additive semantics of `slides` (omitted ids are removed, new ids appended) and clarifies that the returned present URL is members-only, not a shareable link, plus how to actually share. It does not state the permissions/auth required to perform the update, leaving a minor gap.

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?

Purpose is front-loaded in the first sentence, followed by the non-obvious `slides` contract and the return/share caveat. It is somewhat long and the sharing explanation could be trimmed, but every sentence carries information relevant to correct invocation or interpretation.

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?

There is no output schema and no annotations, so the description must cover behavior and return values, and it does explain the return payload (deck id + present URL) and its sharing limitation. The main residual gap is the absence of permission/prerequisite information for a mutation tool.

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. The description adds genuine meaning beyond the schema for `slides` by spelling out the declarative contract (full-list replacement, reorder/add/remove, append order) and reiterating omit/[] behavior, which goes past the schema's own wording.

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 (update) and resource (deck) and enumerates the updatable fields (title, description, slide order). An agent can immediately distinguish this mutation tool from get_deck, create_deck, and list_decks without consulting the schema.

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

Usage Guidelines3/5

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

The description explains how to express reorder/add/remove via the declarative slides list, which is strong implied usage guidance for that parameter. However, it never states when to choose this tool over siblings (e.g., create_deck vs update_deck) or any prerequisites for invoking it, so usage guidance is present but partial.

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

Deploy Server

Other Tools