3db216c628
When a user asks to view cluster status (e.g. "看看机器情况"), the LLM saw non-OK values in the MCP response (a node UNAVAIL, a job PEND/EXIT) and treated them as incidents — proposing unsolicited diagnostic/repair actions and referencing "known bugs". The user only wanted a factual status report. Mitigation at the MCP layer: - Add server instructions (returned to the client in the initialize handshake) stating that the status tools return operational snapshots, that UNAVAIL/PEND/EXIT/UNKWN are normal state, and that the model must not speculate or propose actions unless the user explicitly asks. - Append report-only guidance to the scheduler_list_nodes / list_jobs / cluster_metrics descriptions. Verified: initialize response carries the 857-char instructions; tools/list shows the updated descriptions. Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| cmd | ||
| internal | ||
| go.mod | ||
| go.sum | ||