graph-arch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_impactA | 查询一个图节点的变更影响范围(谁会被这个节点的变更波及)。 何时必须调用:
何时不需要:
参数:
返回: [{id, layer, type, status, summary, path, hops}] 按传播距离排序。 返回的 path 是指针——细节由 skill 按指针从源头加载,不要向本工具索要内容全文。 |
| query_contextA | 图导航:查询节点的邻域导航信息,用于 Agent 诞生后构建工作上下文。 何时必须调用:
何时不需要:
参数:
返回: {id, type, layer, name, summary, path, status, skill_hint, neighborhood} 返回的是导航信息而非内容本身——按 path 指针从源头(git/文档/schema)加载细节。 skill_hint 是处理建议,实际路由由 harness 的 skill_routes.yaml 决定。 |
| submit_graph_intentA | 提交图变更意图请求(开发完成后的必经步骤)。缓存为 pending,git 提交后由 review 核验。 何时必须调用:
何时不需要:
参数:
返回: {status: "pending", task_id, path} 注意: 本工具只缓存不写入——review 失败(git 提交被拒)时 pending 不会进图。 |
| claim_taskA | 认领一个 Hook 分发的任务(多 Agent 防撞车的排他锁定)。 何时必须调用:
何时不需要:
参数:
返回: {status: claimed|rejected, task_id, ...} |
| get_pending_intentsA | 查看待核验的意图请求(review agent 专用)。 何时调用:
何时不需要:
返回: 意图请求列表(完整 JSON) |
| get_pending_tasksA | 拉取任务队列(被动触达的 pull 端)。harness 执行循环中每轮调用。 何时必须调用:
何时不需要:
参数:
返回: 任务列表 [{task_id, source_node, message, subscribers, status, ...}] 对订阅了你的任务: 先 query_impact 评估 → 需响应则 claim_task 后开工 |
| graph_revisionA | 查询当前图版本号(写意图请求时填入 base_revision,用于过期检测)。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
query_impact and query_context are clearly differentiated by their focus (propagation vs. navigation), and the core command/voting tools are distinct. However, get_pending_intents and get_pending_tasks share a similar prefix and both return lists, so an agent could initially confuse them; descriptions mitigate but do not fully eliminate this.
Most tools follow a snake_case verb_noun pattern (query_impact, submit_graph_intent, claim_task, get_pending_tasks, get_pending_intents). graph_revision deviates as a noun-only identifier, and there is minor verb variance (query vs. get vs. submit), but the overall pattern is readable and predictable.
Seven tools is well within the ideal range for a specialized graph/context server. Each tool serves a distinct part of the investigate-assess-claim-submit-review workflow with no obvious redundancy or bloat.
The tool surface covers the core lifecycle: context discovery, impact analysis, task retrieval/claiming, intent submission, pending-intent review, and revision tracking. Minor gaps exist—such as no explicit intent-cancellation or node-detail tool—but query_context and query_impact fill most needs and the workflow appears functional.