endiagram

diff

Compare two system architectures to identify structural differences in topology, roles, and subsystems. Analyze changes between EN syntax descriptions for system analysis.

Instructions

Structural diff between two systems — topology, role, and subsystem 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": {
      "source_a": "<source_a>",
      "source_b": "<source_b>"
    },
    "name": "diff"
  }
}

Input Schema

Name	Required	Description	Default
`source_a`	Yes	EN source code for the first system
`source_b`	Yes	EN source code for the second system

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Mar 20, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool performs a 'structural diff' but doesn't explain what that entails—whether it's read-only, what format the output takes, if there are rate limits, or any side effects. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that front-loads the core purpose ('Structural diff between two systems') and adds specific details ('topology, role, and subsystem changes') without unnecessary elaboration. Every word earns its place.

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

Completeness2/5

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

Given the complexity of comparing two systems and the lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'structural diff' outputs, how to interpret results, or any behavioral traits, making it inadequate for an agent to use the tool effectively without further context.

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

Parameters3/5

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

The schema description coverage is 100%, with clear descriptions for both parameters ('EN source code for the first/second system'). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score for high schema coverage without adding value.

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 clearly states the tool performs a 'structural diff' between two systems, specifying it examines 'topology, role, and subsystem changes.' This provides a specific verb ('diff') and resource ('two systems'), though it doesn't explicitly differentiate from sibling tools like 'analyze_system' or 'distance' that might also compare systems.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context for usage, or exclusions, leaving the agent to infer based on the tool name and parameters alone.

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

Deploy Server