Three tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema clarity, and error handling guidance. list_sessions and read_buffer have acceptable descriptions (60-80 chars), but execute_command lacks detail on side effects. No parameters have descriptions in the schema (only in docstrings). Output schemas are not formally documented, read_buffer returns a string, execute_command returns a dict, but the dict structure is not specified. Error handling returns plain strings or dicts without actionable recovery guidance. No input validation, no enum constraints, no pagination support. Naming is acceptable (verb_noun pattern), but parameter descriptions are missing from JSON schemas entirely.
Execute a command in a specific tmux terminal Args: session_name: Name of the tmux session to execute the command in command: The command to execute Returns: Dictionary with status and message
List all available tmux sessions
Read the buffer content from a specified tmux terminal Args: session_name: Name of the tmux session to read from start_line: Optional starting line number (default is beginning of buffer) num_lines: Optional number of lines to read (default is all lines) Returns: The content of the tmux buffer as a string
Parameter descriptions missing from JSON schemas. Only docstring descriptions exist; schema objects lack 'description' fields for session_name, start_line, num_lines, command. LLMs cannot infer parameter meaning from names alone.
Output schemas not formally documented. read_buffer returns a string (no structure), execute_command returns a dict with 'status' and 'message' fields, but the dict schema is not declared. LLMs cannot plan downstream calls without knowing return structure.
Error responses lack actionable recovery guidance. Errors return plain strings like 'Error: Session not found' or 'Error reading tmux buffer: <stderr>'. No guidance on what the LLM should do next (retry, lookup, ask user).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
execute_command description does not state that it modifies state (sends command to tmux). Agents need to know which calls are irreversible and cannot be safely retried.
No input validation or enum constraints. start_line and num_lines accept any integer; no bounds checking. session_name accepts any string; no validation that session exists before attempting operation (validation happens at runtime, not schema level).