find_dependency_path

GliderMCP

┌ ┐

└ ┘

│

┌ ┐

[architecture]

Finds the shortest direct-project dependency chain between two loaded projects.

Why this tool exists

Monorepo package relationships and import graphs are too large to reconstruct reliably from scattered file reads.

How it helps the agent

The model can reason from package, project, dependency, dependent, path, and cycle facts before editing architecture-sensitive code.

Try it locally in the TGlider playground

Parameters

Name	Type	Required	Description
fromProjectName	string	Yes	Starting loaded project name.
toProjectName	string	Yes	Target loaded project name.

Examples

Explain why one project reaches another

Request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_dependency_path",
    "arguments": {
      "fromProjectName": "web-app",
      "toProjectName": "shared-ui"
    }
  }
}

Response Notes

Returns a compact project dependency path when one is found.

└ ┘