detect_cycles

[architecture]

Detects project-level dependency cycles across the loaded workspace graph.

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

This tool requires no parameters.

Examples

Find project cycles

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

Response Notes

Returns project dependency cycles with compact path evidence.

↑/↓ NavigateEnter OpenSpace Expand