Save plain-English descriptions to the codebase graph
graph_describeSave summaries and change impact notes for pending graph items to .skylos/graph/notes.json. Previous descriptions are kept for comparison, and the graph viewer reads the stored notes.
Instructions
Save descriptions you wrote for items from graph_pending into .skylos/graph/notes.json, where the graph viewer and graph_show read them. A replaced description is kept as the previous one, so readers can see what the code did before. Unknown ids are ignored, and so are impact entries for callers graph_pending did not list with that change. Summaries are capped at 400 characters and impact effects at 300. Writes one local file.
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": {
"items": "<items>"
},
"name": "graph_describe"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Project directory. A relative path resolves against the MCP server's working directory. | . |
| items | Yes | [{"id": ..., "summary": ...}] for code, or [{"id": ..., "before": ..., "after": ..., "same_behaviour": "yes|no|unclear", "why": ..., "impact": [{"id": "<caller id>", "effect": "<one sentence>"}]}] for changes; ids come from graph_pending, impact ids from that change's callers |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |