Deterministic GKX validation, projection, graph, and source-content-read-only Navigation with explicit governance boundaries.
GKOS-Engine exposes 8 tools with severe definition gaps. Most tools lack visible input schemas in the provided source code, only 2 tools (scanCorpus, validatePhase3KbPath) show partial schema hints. Descriptions are present but generic (50-150 chars), failing to explain WHEN to use each tool or what happens on error. No tool shows output schema documentation. Tool names are non-standard (health, proposals, scanCorpus, buildBlock) and do not follow verb_noun convention. No parameter descriptions visible for most tools. Error handling, security constraints, and composition guidance are absent. This is a domain-specific engine (GKX validation, corpus hashing, build blocks) but the MCP interface is underdeveloped for agent use.
Generate deterministic build block with engine_version, policy_hash, corpus_hash, and generated_at timestamp
Compute stable corpus hash over sorted list of (path, content_hash) pairs
Create HTTP request handler for local GKOS service with authorization, CORS, rate limiting, and MCP runtime support
GET /health endpoint returning server health status, contract version, program version, and configuration state
POST /v1/proposals endpoint for DSPy-backed GKOS proposal generation with optional Bearer token authentication
Inventory and validate TOML settings for GKOS runtime configuration with optional config file validation
Read-only corpus scan with deterministic ignore rules matching all surfaces
No visible input schemas for 6 of 8 tools. Only scanCorpus and validatePhase3KbPath show partial schema hints; health, proposals, corpusHash, buildBlock, runSettingsCli, and createLocalServiceRequestHandler have no documented input structure.
Tool names do not follow verb_noun convention. 'health', 'proposals', 'scanCorpus', 'buildBlock' are nouns or unclear actions. LLMs cannot infer intent from names alone. Should be: get_health, generate_proposals, scan_corpus, generate_build_block.
No output schemas documented for any tool. Agents cannot plan downstream calls or extract required fields. E.g., does health() return {status, version, config} or a string?
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | <=2025-11-25 | v2 |
Phase-3-only local vault grammar validation; performs no filesystem access
Descriptions lack WHEN/WHY guidance and error recovery hints. E.g., 'POST /v1/proposals endpoint for DSPy-backed GKOS proposal generation' does not explain when to call it, what inputs it needs, or what to do if it fails.
No parameter descriptions visible. scanCorpus accepts 'dir' and 'options' but no description explains what 'options' contains, what values are valid, or constraints on 'dir' (absolute vs relative, must exist?).