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

list_diagram_pieces

Returns all diagram pieces as a JSON array with file, slug, title, function path, group, file path, and existence status, so agents can inspect available diagram components.

Instructions

List all diagram pieces as a JSON array of {file, slug, title, function_path, group, file_path, exists}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_diagram_pieces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose the exact return shape, which is the most important behavior here. It stops short of stating that this is a pure read with no side effects, whether results are ordered, or what the `exists` flag actually checks (a disk probe, presumably).

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 front-loaded sentence with no filler; the return-field list is dense but each token is informative. Nothing could be removed without losing meaning.

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?

There is no output schema, so the description correctly compensates by spelling out the returned keys, and a zero-parameter read tool needs little else. Minor gaps remain around ordering, pagination/volume, and the semantics of `exists`.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is empty and fully self-explanatory.

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?

"List all diagram pieces" gives a specific verb and resource, and the enumerated return fields ({file, slug, title, function_path, group, file_path, exists}) make the scope concrete. It implicitly contrasts with singular siblings like get_diagram_piece, though it never names them.

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

Usage Guidelines3/5

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

"List all" implies the use case (enumerate the whole collection), which contrasts by inference with get_diagram_piece for a single piece. There is no explicit when-to-use, when-not, or named alternative, so routing must be inferred from sibling names.

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