get_project_dependencies

GliderMCP

┌ ┐

└ ┘

│

┌ ┐

[architecture]

Lists direct workspace project dependencies for a loaded project.

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
projectName	string	Yes	Loaded project name.

Examples

List dependencies for one project

Request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_project_dependencies",
    "arguments": {
      "projectName": "app"
    }
  }
}

Response Notes

Returns direct project dependency edges.

└ ┘