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

create_diagram_piece

Creates a new STAR diagram piece from a template, defining its title, slug, source path, and optional inputs, outputs, and dependencies for architecture visualization.

Instructions

Create a new STAR diagram piece from template

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": {
      "slug": "<slug>",
      "title": "<title>",
      "function_path": "<function_path>"
    },
    "name": "create_diagram_piece"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug for the piece (e.g., 'api-handler')
groupNoGroup for viewer navops
titleYesHuman-readable title
inputsNoInput sources
outputsNoOutputs
dependenciesNoDependencies (services, APIs)
function_pathYesSource file path (e.g., 'src/api/handler.py')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden for a write operation, yet it discloses no side effects, no failure/duplicate-slug behavior, no permission requirements, and no explanation of what 'from template' actually scaffolds or which defaults are populated. Only the fact that it is a creation operation is conveyed.

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?

A single short sentence with the action front-loaded and no padding. It is efficient, though the brevity here is closer to under-specification than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter creation tool with no annotations and no output schema, the description is far too thin — it omits required-field implications, what the returned piece identifier looks like, and how the created piece relates to build_viewer. The structured schema covers parameter shapes but not the surrounding behavior.

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 100%, so all seven parameters including the enums and nested input/output/dependency arrays are documented in the schema itself; the baseline of 3 applies. The description adds nothing beyond the schema, and 'from template' slightly muddies matters by implying a parameter that does not exist.

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 description pairs a specific verb ('Create') with a specific resource ('STAR diagram piece'), so an agent can tell what it produces. However, 'from template' is undefined — no template parameter exists in the schema — which leaves the creation mechanism ambiguous rather than distinguishing it clearly from update_diagram_piece.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of update_diagram_piece or list_diagram_pieces, no preconditions (e.g., piece must not already exist), and no note about the build_viewer workflow. The agent must infer all usage context from the sibling names alone.

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