Skip to main content
Glama
Sign In
mcp-archimate

mcp-archimate

by byrondelgado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

summarize_model

Read-only

Get a summary of the active ArchiMate model including element, relationship, and view counts, plus per-view node and connection totals. Useful for verifying model generation results.

Instructions

Summarize the active model: counts, view summaries, totals.

Useful for verifying generation results without dumping full XML.

Returns:
    Success envelope with `data` containing model name, total
    element/relationship/view counts, and per-view node and
    connection counts.

Errors:
    `ModelNotFoundError` if no model is active.

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": "summarize_model"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the annotations (readOnlyHint=true) by detailing the return structure (success envelope with data containing model name, counts) and potential errors (ModelNotFoundError). No contradictions with annotations.

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?

The description is concise yet comprehensive: three paragraphs covering purpose, usage, return values, and errors. Every sentence adds value, and it is well-structured for quick reading.

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?

Given no parameters and the presence of an output schema (mentioned in description), the description fully covers all necessary details for an agent to understand the tool's behavior, return structure, and error conditions.

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 no parameters and 100% schema coverage, the baseline is 4. The description effectively explains what the tool does without needing parameter details, fulfilling the need for completeness.

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 clearly states the tool summarizes the active model with counts, view summaries, and totals. It distinctly differentiates from sibling tools like 'summarize_view' by focusing on the entire model.

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?

The description specifies that the tool is useful for verifying generation results without dumping full XML, providing a clear context. However, it does not explicitly mention when not to use it or suggest alternatives among the many sibling tools.

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