A Rust-based system for container orchestration and remote execution with FFI bindings and dataplane management
Dory exposes 5 tools with severe definition gaps. The 'run' tool has a detailed schema with 6 parameters (executableURL, arguments, workingDirectoryURL, environment, timeout, outputPolicy), but 3 of 5 tools (kubectl, docker, dorydctl) have NO visible input schemas and NO descriptions in the source. The 'userFacingDoryCommand' tool has a schema but minimal description. Tool names are generic ('run', 'kubectl', 'docker') and do not follow verb_noun conventions. No error handling guidance, no output schemas documented, and no parameter validation rules visible. This is a low-maturity implementation.
Resolves the docker CLI tool from bundled or system installation
Resolves the dorydctl CLI tool from user home, homebrew, or system installation
Resolves the kubectl CLI tool from bundled, component, or system installation
Executes a tool command with bounded output, timeout handling, and concurrent stream draining
Resolves the stable user-facing dory command from home directory, homebrew, or system installation
3 of 5 tools (kubectl, docker, dorydctl) have no visible input schemas and no descriptions.
Tool names do not follow verb_noun convention. 'run', 'kubectl', 'docker' are generic or bare nouns. Should be 'execute_command', 'resolve_kubectl', 'resolve_docker' to clarify intent.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing return structure.
'run' tool description lacks error handling guidance. No mention of what happens on timeout, non-zero exit, or output overflow. Agents cannot recover from failures.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 29 | 2026-07-28+ | v2 |
'run' tool accepts 'executableURL' and 'workingDirectoryURL' as URL types but no validation rules or format constraints documented. LLMs may pass invalid paths.