You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: docs/mcp.md and pkg/mcp_server/README.md say to call server_info at session start, the server says on demand #930
pkg/mcp_server/content/tools/server_info.md (the tool description): "Call on demand - eg to diagnose a refused/gated operation or check version-specific behavior. Not needed at session start or before queries."
pkg/mcp_server/content/instructions/00-stackql.md line 7 (the server instructions): "Call it on demand - to diagnose a refused or gated operation, before relying on dialect-specific functions, or when reporting a problem - not as a session-start step, and never before queries."
What the docs say:
docs/mcp.md line 132, the comment above the server_info example in the stackql_mcp_client walkthrough: ## Server identity and runtime metadata. Call once at session start.
docs/mcp.md line 181, the server_info row of the tool table: "... read-only flag. Call once at session start."
pkg/mcp_server/README.md line 210, the server_info row of the tool table: "... read-only flag. Call once at session start." This row also leaves mode out of the fields, which the tool description and docs/mcp.md include.
Suggested change: replace "Call once at session start." in all three places with the tool description's wording ("Call on demand, for example to diagnose a refused or gated operation or to check version-specific behavior; not needed at session start or before queries"), and add mode to the README row.
The stackql.io docs (/mcp/server_info, /command-line-usage/mcp) were updated to the on-demand wording on 2026-11-16.
Activity
jeffreyaven commentedon Nov 18, 2026
Resolved in PR #936, merged as 256187f.