Skip to main content
Glama
noit-mcp-server
by Yuki-az-23

update_diagram_piece

Updates an existing diagram piece in place for title, function path, or group changes, and rebuilds the diagram from supplied inputs, dependencies, and outputs; include all spokes to retain.

Instructions

Update an existing diagram piece. title/function_path/group are changed in place. If any of inputs/dependencies/outputs is given, the diagram is rebuilt from the given lists, so pass all spokes the piece should keep.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>"
    },
    "name": "update_diagram_piece"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesFilename (e.g., '01-api-handler.md')
groupNo
titleNo
inputsNo
outputsNo
dependenciesNo
function_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 disclose the critical non-obvious behavior: three fields mutate in place while the three list fields trigger a destructive rebuild of the diagram. It omits return value, error behavior, and whether the file must already exist, which keeps it from a 5.

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, zero filler, and the safe path (in-place scalar edits) is stated before the dangerous path (full rebuild). Every clause conveys operational information.

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 a 7-parameter mutation tool with no annotations and no output schema, the description covers the highest-risk behavior well and warns about data loss. Remaining gaps are enum semantics and failure modes, which are secondary to correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description must compensate, and it does for inputs/dependencies/outputs by explaining the rebuild semantics. However it adds nothing about the group enum values, the dependency type enum (dep/extSvc), or the shape of the spoke objects, leaving several parameters documented only by bare schema types.

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?

States a specific verb and resource ("Update an existing diagram piece") and enumerates which fields are modified in place. The contrast with create_diagram_piece is left implicit, but the verb makes the boundary obvious enough.

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 clear conditional rule: use scalar fields for lightweight edits, but supplying inputs/dependencies/outputs rebuilds the diagram, so all spokes that should survive must be passed. That is real when-to-use guidance for the main decision point, though it does not mention the other sibling tools or preconditions such as the piece existing.

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