A monorepo containing a multi-app agent system with MCP server discovery, connector management, and tool orchestration capabilities
Zeno Agent exposes 4 CLI tools via MCP with minimal documentation. All tools have descriptions (10-50 chars), but lack depth and actionable guidance. Input schemas are present but sparse: parameters have types and brief descriptions, but lack enums, constraints, or format specifications. No output schemas are documented. Error handling is absent, no recovery guidance, no categorization of failures. Tool names follow verb_noun convention (connector_refresh_tools, connector_tool_list, connector_tool_set, connector_tool_bulk), which is good, but descriptions are generic and do not explain WHEN to use each tool or what distinguishes them. Parameters like 'permission' and 'category' accept constrained values but are not declared as enums, forcing LLMs to guess valid options. No security annotations, no idempotency hints, no audit trail guidance.
Re-discover tools for a connector by enqueuing a connector_refresh_tools command
Set permission for all tools in a category
List tools and their permissions for a connector
Set permission for a single tool
No output schemas documented. LLMs cannot plan downstream calls or extract structured data from responses.
Constrained parameters (permission, category) lack enum declarations. LLMs must guess valid values instead of selecting from a machine-readable list.
Descriptions are too brief (10-50 chars) and lack actionable context. No explanation of WHEN to use each tool, what distinguishes them, or what happens on success/failure.
No error handling guidance. LLMs receive no recovery hints, error categorization, or actionable next steps on failure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot determine which tools are safe to retry or have side effects.