Skip to main content
Glama
mm6502

Enterprise Architect MCP Server

by mm6502
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ea_list_diagrams

Read-only

List diagrams from an Enterprise Architect model, filtering by package, diagram type, or name substring. Supports paging with continuation and type-based breakdown to navigate large result sets.

Instructions

List diagrams in the model, optionally filtered by package, diagram type, and/or name substring. Each entry in results carries diagramId, name, type, packagePath, and eaGuid. Diagrams are ordered by the model's internal identity — stable but artificial, neither alphabetical nor the analyst's tree order — so adjacency carries no meaning. Walk a large result set with offset rather than a larger limit; while rows remain, continuation names the next call. When far more diagrams match than one window can hold, breakdown reports how many each type holds, so the next call can narrow by diagramType instead of paging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 50)
offsetNoZero-based index of the first result to return (default 0). Page by re-calling with the offset carried in continuation.
packageIdNoFilter to diagrams in this package
diagramTypeNoFilter by diagram type (e.g., Logical, Use Case, Sequence, Activity, Component)
nameContainsNoFilter to diagrams whose name contains this substring (case- and diacritic-insensitive across European Latin alphabets)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.0.0
    • addedInput schema / properties / diagramType
      Added value: +{
+  "description": "Filter by diagram type (e.g., Logical, Use Case, Sequence, Activity, Component)",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default 50)"New value: +"Maximum number of results to return (default 50)"
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / nameContains / description
      Previous value: -"Filter to diagrams whose name contains this substring (case-insensitive across Slovak alphabet)"New value: +"Filter to diagrams whose name contains this substring (case- and diacritic-insensitive across European Latin alphabets)"
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Zero-based index of the first result to return (default 0). Page by re-calling with the offset carried in continuation.",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv2.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that ordering is stable but artificial, that adjacency carries no meaning, that continuation names the next call, and that breakdown reports type counts. These are non-obvious behavioral details an agent needs to interpret results correctly.

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?

Four dense sentences, each earning its place: purpose+filters, result fields, ordering caveat, pagination strategy, and breakdown guidance. The most important information is front-loaded, and there is no filler or repetition of the schema.

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 read-only listing tool with no output schema, the description covers the entry fields returned, ordering semantics, pagination mechanism, and a narrowing strategy for large result sets. An agent can call the tool and interpret results correctly without additional context.

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?

With 100% schema description coverage, the baseline is 3; the description adds meaning by explaining the offset/continuation paging pattern and recommending smaller batches. It also clarifies the filtering intents (package, diagram type, name substring) and the result fields tied to the call, going slightly beyond the raw schema.

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

Purpose5/5

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

The description opens with a specific verb and resource ('List diagrams in the model') and enumerates the optional filters (package, diagram type, name substring), which clearly scopes the operation. The result fields and ordering caveat further distinguish it from sibling tools like ea_list_elements or ea_search, even though no sibling is named.

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?

It gives practical guidance: use offset rather than larger limit for large result sets, follow continuation, and use breakdown to narrow by diagramType instead of paging. It does not explicitly compare against sibling tools such as ea_search or ea_get_diagram_elements, so the when-to-use-this-versus-alternative guidance is slightly incomplete.

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

Deploy Server

Other Tools