Code that matters most to the files you are changing
graph_relevantFind the functions and classes most relevant to files you plan to change, ranked by importance with signatures, locations, and call relationships, so you know what else to read before editing.
Instructions
The functions and classes elsewhere in the repository that matter most to the given files, most important first, cut to a token budget: each with its signature, file and line, plain-English summary, how it relates to the files (calls them, called by them) and its area. Use it before editing to know what else to read. Returns JSON. Read-only and local.
Works without SKYLOS_API_KEY and has no daily limit: it reads the repository on this machine and sends nothing to Skylos Cloud.
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": {
"files": "<files>"
},
"name": "graph_relevant"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Project directory. A relative path resolves against the MCP server's working directory. | . |
| files | Yes | Files you are about to change, relative to the repository root | |
| budget | No | Token budget for the answer, 100-20000 |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |