An automation layer for pi: cron + stateful loops with a triage inbox, maker/checker verification, dynamic triggers, MCP notifications and tools, lifecycle hooks, session archives. A non-invasive pi extension.
pi-loops defines 13 tools with mixed quality. Core cron/trigger tools (cron_create, cron_list, cron_run, cron_set, cron_remove, trigger_create, trigger_set, triggers_list, trigger_remove) have clear verb-noun naming and reasonable descriptions (50-150 chars). Input schemas are present with typed parameters and descriptions. However, several critical gaps reduce the score: (1) cron_create's 'schedule' parameter is typed as object with only a description, no nested schema properties visible, making validation unclear; (2) error handling descriptions are absent, tools don't explain what happens on failure or how to recover; (3) output schemas are completely undocumented, LLMs cannot predict what fields to expect from list/create operations; (4) three test tools (demo_status, echo, slow, fail) are trivial and lack production-grade descriptions; (5) no tool declares idempotency or destructiveness hints in the schema itself (only in metadata). Naming is strong (verb_noun pattern), but schema completeness and error guidance are weak.
Create a new cron job with a schedule, prompt, and optional configuration
List all cron jobs with their status, schedule, and next run time
Delete a cron job
Manually trigger a cron job to run immediately
Modify an existing cron job's configuration
How many heartbeats this demo server has pushed
Echo text back
Returns isError
Output schemas completely undocumented. cron_list, triggers_list, and cron_create return values are not specified. LLMs cannot predict response structure or chain tools effectively.
Complex parameter 'schedule' in cron_create typed as object with no nested schema properties visible. Validation rules for cron expressions are unclear to LLMs.
No error handling guidance. Tools do not document what errors are possible, whether they are retryable, or what the LLM should do next on failure.
Test tools (demo_status, echo, slow, fail) have minimal descriptions (<40 chars) and lack production context. These should be removed or properly documented.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
Never answers
Create a new dynamic trigger rule
Delete a dynamic trigger rule
Modify an existing dynamic trigger rule
List all dynamic trigger rules with their status and configuration
Tool annotations (destructiveHint, idempotentHint) not visible in schema. cron_remove and trigger_remove are destructive but lack explicit schema hints.