A collection of CLI tools for interacting with external APIs (Discourse, Linear, Slack) - designed to be used by AI agents
14 tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema clarity, and error handling guidance. Tool names follow verb_noun convention (discourse-topics-list, linear-issues-list, slack-messages-list), which is good. However, descriptions are minimal (10-50 chars typically), parameter descriptions lack detail on constraints/formats, and no visible output schema documentation. No error recovery guidance. Schemas present but sparse, many parameters lack type constraints (e.g., 'order' in discourse-topics-list accepts free-form string with no enum). No evidence of idempotency hints, permission gates, or audit logging. STDIO transport caps protocol readiness at 50, but definition quality itself is weak.
Create a new post or reply in a Discourse forum
Delete a post from a Discourse forum
Get the latest posts from a Discourse forum
Get a specific topic and its posts from a Discourse forum
List topics from a Discourse forum
Create a new issue in Linear
Get a specific issue from Linear
Update an existing issue in Linear
Descriptions are too brief (10-50 chars). Rubric baseline is 194 chars avg; LLMs need context on WHEN to use each tool and what it returns. E.g., 'List topics from a Discourse forum' lacks guidance on filtering, pagination, or result structure.
Parameter descriptions lack constraint details. E.g., 'order' in discourse-topics-list accepts free-form string with no enum (latest, views, likes, etc. mentioned in description but not in schema). 'priority' in linear-issue-create/update says '0-4' in description but no min/max in schema. LLMs cannot parse text constraints reliably.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
List issues from Linear
Get information about a specific Slack channel
List Slack channels
Post a message to a Slack channel
List messages from a Slack channel
List Slack workspace users
No output schema documentation visible. Rubric requires documented return types for 100% of A+ tools. Cannot verify what fields each tool returns, making it impossible for LLMs to plan downstream calls or extract required IDs for chaining.
No error handling guidance. Rubric requires error responses to tell LLM what to do next (retryable? user-fixable? fatal?). No evidence of recovery guides, error classification, or actionable error messages in source code.
Destructive tools (discourse-post-delete) lack confirmation/dry-run pattern. Rubric requires irreversible operations to support confirmation step to prevent catastrophic agent errors.