excalidraw-architect-mcp

Overview Schema Source Related Servers Discussions Admin

kg_path

Trace the shortest dependency path between two services to clarify how they connect. Enter the service IDs to get the minimal route, simplifying dependency analysis.

Instructions

Trace the shortest dependency path between two services.

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": {
      "from_id": "<from_id>",
      "to_id": "<to_id>"
    },
    "name": "kg_path"
  }
}

Input Schema

Name	Required	Default
`to_id`	Yes
`from_id`	Yes
`graph_path`	No	.claude/architecture.md

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.3Jun 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Behavior is implied but not detailed: e.g., what happens if no path exists, how cycles are handled, or what format the path returns. No annotations exist to supplement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise single sentence with no waste, but it sacrifices detail that could be added without expanding length.

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?

Despite having an output schema, the description lacks context on ID types, graph_path default, and error handling. Incomplete for a tool with many siblings and no schema comments.

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 has 0% description coverage; description only hints at 'two services' (from_id, to_id) but does not explain graph_path or parameter formats beyond the schema defaults.

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 verb 'Trace' and the resource 'shortest dependency path between two services', which distinguishes it from sibling tools like kg_link or kg_info.

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 on when to use this tool vs alternatives such as kg_info or kg_render. No exclusion criteria or prerequisites mentioned.

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