Skip to main content
Glama
mm6502

Enterprise Architect MCP Server

by mm6502
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ea_list_elements

Read-only

List elements in a package, optionally filtered by object type, and page through large result sets using offset and continuation to locate a specific element.

Instructions

List elements within a package, optionally filtered by object type. elements is a lightweight list (ID, type, name, alias, stereotype), grouped by element type and then ordered by the model's internal identity. That order is stable but artificial — neither alphabetical nor the analyst's tree order — so adjacency carries no meaning. Walk a large package with offset rather than a larger limit; while rows remain, continuation names the next call. When far more elements match than one window can hold, breakdown reports how many each type holds, so the next call can narrow by objectType 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.
packageIdYesThe Package_ID to list elements from
objectTypeNoFilter by object type (e.g., Class, UseCase, Activity, Screen)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.0.0
    • 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"
    • 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 readOnly annotation, the description discloses that ordering is stable but artificial, that adjacency carries no meaning, and that `continuation` and `breakdown` appear as paging aids. This is valuable behavioral context that the schema and annotations alone do not provide.

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?

Three dense sentences deliver exactly the needed information: what is returned, how ordering behaves, and how to page. Nothing is redundant, and key behavioral caveats are front-loaded.

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?

With no output schema, the description carries the burden of explaining return values. It covers the element fields, grouping, ordering, pagination through `continuation`, and the `breakdown` mechanism, making the tool's contract clear enough to call confidently.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds meaningful usage semantics for `offset`, `limit`, and `objectType`, explaining why one pagination strategy is preferable over another and how `breakdown` should drive narrowing.

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 states a specific verb and resource ('List elements within a package') and immediately clarifies the lightweight nature of the result. It also distinguishes itself from single-element retrieval and broader search by describing exact output fields and grouping.

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 provides clear usage context for pagination, explaining to use `offset` rather than a larger `limit` and to narrow by `objectType` when `breakdown` indicates many matches. It does not explicitly name alternatives among siblings, but the context is clear enough for tool selection.

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