Skip to main content
Glama

livediagram

by app.livediagram.mcp
OverviewDiscussionsAdmin

Share a document (deprecated)

share_diagram

Deprecated: use share_document instead; this name is removed on 2027-04-30. It takes the same input as share_document.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlYesThe share link. Opening it needs no sign-in.
roleYesWhat the link grants.
expiresAtYesWhen the link stops working, as a ms epoch; null when it never expires.
documentUrlYesLink that opens the document in the livediagram editor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +{}
    • removedInput schema / properties / documentId
      Removed value: -{
-  "description": "The document to share (from find_documents / read_document).",
-  "type": "string"
-}
    • removedInput schema / properties / expiry
      Removed value: -{
-  "description": "When the link stops working. Defaults to \"never\" (until revoked).",
-  "enum": [
-    "never",
-    "week",
-    "month",
-    "sixMonths"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / role
      Removed value: -{
-  "description": "What the link grants. \"participate\" (default): recipients add stickies, write and vote but cannot reshape it; right for a retro or a workshop. \"view\": they only look, with no comments or votes. \"edit\": they can change anything. No sign-in is needed to open any.",
-  "enum": [
-    "view",
-    "participate",
-    "edit"
-  ],
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "documentId"
-]
  2. Changed3 schema fields changed
    • changedInput schema / properties / role / description
      Previous value: -"What the link grants. \"view\" (default) — recipients can open and read but not change it; safest for just showing your work. \"edit\" — recipients can also edit. No sign-in is needed to open either."New value: +"What the link grants. \"participate\" (default): recipients add stickies, write and vote but cannot reshape it; right for a retro or a workshop. \"view\": they only look, with no comments or votes. \"edit\": they can change anything. No sign-in is needed to open any."
    • changedInput schema / properties / role / enum
      Previous value: -[
-  "view",
-  "edit"
-]New value: +[
+  "view",
+  "participate",
+  "edit"
+]
    • changedOutput schema / properties / role / enum
      Previous value: -[
-  "view",
-  "edit"
-]New value: +[
+  "view",
+  "participate",
+  "edit"
+]
  3. Changed6 schema fields changed
    • removedInput schema / properties / diagramId
      Removed value: -{
-  "description": "The diagram to share (from find_diagrams / read_diagram).",
-  "type": "string"
-}
    • addedInput schema / properties / documentId
      Added value: +{
+  "description": "The document to share (from find_documents / read_document).",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "diagramId"
-]New value: +[
+  "documentId"
+]
    • removedOutput schema / properties / diagramUrl
      Removed value: -{
-  "description": "Link that opens the diagram in the livediagram editor.",
-  "type": "string"
-}
    • addedOutput schema / properties / documentUrl
      Added value: +{
+  "description": "Link that opens the document in the livediagram editor.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "url",
-  "role",
-  "expiresAt",
-  "diagramUrl"
-]New value: +[
+  "url",
+  "role",
+  "expiresAt",
+  "documentUrl"
+]
  4. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds lifecycle transparency (deprecation and removal date) that annotations do not carry, but says nothing about what sharing actually mutates (e.g. permission changes) or any auth requirements.

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?

A single sentence with the deprecation warning front-loaded, followed by the replacement and the sunset date. No filler, and the most decision-relevant fact comes first.

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?

For a zero-parameter deprecated alias with an output schema already defined, the description covers everything needed: identity, replacement, removal date, and input equivalence. Nothing an agent needs to avoid or correctly route around this tool 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?

The schema exposes zero named properties with additionalProperties allowed, so the field list is effectively opaque. The statement "takes the same input as share_document" is therefore valuable, telling the agent where to find the real parameter contract rather than leaving it unknown.

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 title and description identify this as the deprecated alias that shares a document, and it explicitly names the replacement, share_document, so an agent can distinguish it from the other share_* siblings. It is clear what the tool does, though the description leans on the sibling's semantics rather than restating the operation's effect.

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?

It gives explicit routing guidance ("use share_document instead") plus a hard cutoff date ("removed on 2027-04-30"), which is exactly the when/when-not-to-use information an agent needs. An agent can decide to avoid this tool entirely based on the text alone.

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

All livediagram toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources