Skip to main content
Glama

umlforge_stakeholder_arch

Read-only

Create C4 architecture diagrams to communicate system design to mixed technical and non-technical audiences, including context, container, and component views.

Instructions

Generate a C4 architecture diagram for a mixed technical/non-technical audience.

USE THIS WHEN:

  • You are designing or presenting a system to stakeholders (CTO, investors, board)

  • You need a high-level picture of a system you are planning or explaining

  • You want Context + Container + Component diagrams in one call

NOT FOR:

  • Analysing code that already exists → use umlforge_reverse_engineer

  • Tracing a specific API request across services → use umlforge_api_sequence

  • Infrastructure and deployment topology → use umlforge_deployment

  • Security threat modelling → use umlforge_threat_model

Produces:

  • C4 Context: system boundary, external actors, primary integrations

  • C4 Container: deployable units, tech stack labels, communication protocols

  • C4 Component: internals of the most complex container

  • (report_mode=True) Architecture Communication Notes: audience fit, communication gaps, clarity quick wins

Args: system_description: What the system does, who uses it, its major components. audience_description: Who will read this (e.g. "CTO and non-technical board", "backend engineers new to the system"). report_mode: True → also produce Architecture Communication Notes. Pro/Team/Enterprise only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_modeNo
system_descriptionYes
audience_descriptionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations (readOnlyHint=true) already indicate no state modification. The description adds context on outputs (diagrams, optional notes) without contradicting annotations. No side effects or permissions mentioned, but sufficient given annotation coverage.

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 well-structured with clear sections (purpose, conditions, output, args). Every sentence adds value, and the length is appropriate for the detail provided.

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 the presence of an output schema and the detailed description covering purpose, usage, and parameters, the description is complete for an agent to decide when and how to invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description provides detailed explanations for each parameter (system_description, audience_description, report_mode) with examples and constraints, adding significant meaning beyond the 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 clearly states the tool generates C4 architecture diagrams for mixed audiences. It distinguishes from siblings by listing specific alternatives in the NOT FOR section (e.g., umlforge_reverse_engineer, umlforge_api_sequence).

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

Usage Guidelines5/5

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

Explicit USE THIS WHEN and NOT FOR sections provide clear guidance on when to use this tool versus alternatives, with specific sibling tool names for exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dave1362/umlforge-connector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server