Skip to main content
Glama
yenchieh

DiagramZu

by yenchieh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_deck

Update a deck's title, description, and slide order by sending the full ordered list of diagram IDs; omitted IDs are removed, new ones appended.

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
titleNoDeck title shown in the deck list and above the presentation.
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. Addedv0.0.4

TDQS

A4.7/5.0
Behavior5/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 so thoroughly: explains the declarative slides behavior (omitted ids removed, new ids appended), the return value (deck id and present URL), the URL's non-shareable nature, and the required sharing workaround. No side effects are left unmentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, then details on the most complex parameter, then return value and sharing. No wasted words; every sentence adds needed information.

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?

The tool has 4 parameters (1 required), no output schema, and no annotations. The description covers the tricky slides semantics, the return value, and the sharing caveat. The schema covers the simple parameters. Nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so the baseline is 3. The description adds significant value by explaining the declarative semantics of the 'slides' parameter, which goes beyond the schema's description of 'complete ordered list'. This extra guidance justifies a 4.

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 and resource ('Update a deck') and enumerates the mutable fields (title, description, slide order). Clearly distinguishes from siblings like create_deck and get_deck.

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?

Provides clear context for when to use this tool (updating existing decks) and elaborates on how the declarative slides parameter works. Does not explicitly name alternatives or exclusions, but the context is sufficient to route correctly.

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