Skip to main content
Glama
Sign In

livediagram

by app.livediagram.mcp
OverviewDiscussionsAdmin

Rename a document or tab (deprecated)

rename_diagram

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idNoThe renamed document id (document renames).
urlNoLink that opens the document (document renames).
nameYesThe stored name (shortened if it was over the cap).
tabIdNoThe renamed tab id (tab renames).
renamedYesWhether the document or one of its tabs was renamed.

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 rename (from find_documents / read_document).",
-  "type": "string"
-}
    • removedInput schema / properties / name
      Removed value: -{
-  "description": "The new name. Keep it short: at most 60 characters. A longer name is shortened at a word boundary with an ellipsis.",
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / tabId
      Removed value: -{
-  "description": "Rename this tab within the document instead of the document itself.",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "documentId",
-  "name"
-]
  2. Changed8 schema fields changed
    • removedInput schema / properties / diagramId
      Removed value: -{
-  "description": "The diagram to rename (from find_diagrams / read_diagram).",
-  "type": "string"
-}
    • addedInput schema / properties / documentId
      Added value: +{
+  "description": "The document to rename (from find_documents / read_document).",
+  "type": "string"
+}
    • changedInput schema / properties / tabId / description
      Previous value: -"Rename this tab within the diagram instead of the diagram itself."New value: +"Rename this tab within the document instead of the document itself."
    • changedInput schema / required
      Previous value: -[
-  "diagramId",
-  "name"
-]New value: +[
+  "documentId",
+  "name"
+]
    • changedOutput schema / properties / id / description
      Previous value: -"The renamed diagram id (diagram renames)."New value: +"The renamed document id (document renames)."
    • changedOutput schema / properties / renamed / description
      Previous value: -"Whether the diagram or one of its tabs was renamed."New value: +"Whether the document or one of its tabs was renamed."
    • changedOutput schema / properties / renamed / enum
      Previous value: -[
-  "diagram",
-  "tab"
-]New value: +[
+  "document",
+  "tab"
+]
    • changedOutput schema / properties / url / description
      Previous value: -"Link that opens the diagram (diagram renames)."New value: +"Link that opens the document (document renames)."
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false), and the rename semantics are consistent with a non-destructive mutation. The description adds real lifecycle context (deprecated, removal date), but says nothing about what the call actually changes on the document/tab.

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 that front-loads the deprecation warning, then the replacement, then the deadline. No filler; every clause carries information the agent needs.

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?

An output schema exists, so return values need not be explained, and for a deprecated zero-param alias the description covers the essentials (superseded by what, until when, same contract). Only the name/title resource mismatch leaves a small gap.

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?

Zero parameters, so baseline is 4. The line 'It takes the same input as rename_document' is a useful pointer to the aliased schema, though it adds little beyond the already-empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name (rename_diagram) and title (Rename a document or tab) point at different resources, creating genuine ambiguity about what this alias renames. The description never states the operation itself, leaning entirely on the sibling rename_document to supply the verb+resource.

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?

Explicitly routes the agent away: 'use rename_document instead', with a hard removal date (2027-04-30) so the agent knows not to build a dependency on this name. This is exactly the when-not/alternative guidance the dimension asks for.

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
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources