Skip to main content
Glama
Sign In
C4 Architect

C4 Architect

by zrack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

compare_architecture_graphs

Compare two saved architecture graphs at one abstraction level to report full change counts with bounded detail; timestamps and scan-root location are ignored.

Instructions

Compare two saved graphs at the same abstraction level. Reports full change counts with bounded detail; timestamps and scan-root location do not create changes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "beforePath": "<beforePath>",
      "afterPath": "<afterPath>"
    },
    "name": "compare_architecture_graphs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
maxBytesNo
afterPathYes
beforePathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0-alpha.1

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: change counts are complete while detail is bounded, and timestamps and scan-root location are explicitly ignored when detecting changes. It doesn't state whether the operation is read-only or how the bounds are enforced, which keeps it below a 5.

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?

Two dense sentences with zero filler, and the core comparison statement is front-loaded before the change-detection caveat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description only partly indicates what a caller gets back ('full change counts with bounded detail'). The critical semantics of limit and maxBytes and the meaning of the two path parameters are missing, which is a real gap for a four-parameter tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all four parameters. 'Bounded detail' hints at limit and maxBytes but gives no meaning to beforePath, afterPath, or how limit and maxBytes interact, leaving three of four parameters undocumented anywhere.

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?

The description states a specific verb and resource ('Compare two saved graphs') plus a scope constraint ('at the same abstraction level'), which clearly separates it from siblings like render_architecture_graph and query_architecture_graph. It never explicitly says the graphs are architecture graphs, but the tool name carries that.

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?

The prerequisite that both graphs must be at the same abstraction level implies when this tool is applicable, but there is no explicit guidance on when to use it versus query_architecture_graph or get_architecture_summary, and no stated exclusions.

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