Loading ToolBench
MCP server for hex.pm and hexdocs.pm: search, inspect, compare, audit, and discover Elixir/Erlang packages, browse docs, and check dependencies for vulnerabilities.
Most tools (20/24) lack visible input schemas and descriptions in the provided source. Only 4 tools (toolbox_group, toolbox_category, toolbox_trending, toolbox_search) have documented schemas and descriptions. Tool names follow verb_noun convention (search, info, versions, release) but many lack actionable descriptions. No evidence of error handling guidance, output schema documentation, or parameter validation rules. The server exposes 24 READ_ONLY tools but provides minimal LLM-facing metadata to guide tool selection and composition.
20 of 24 tools lack visible input schemas and descriptions. Only toolbox_* tools (4/24) have documented parameters and descriptions. Cannot verify schema completeness for search, info, versions, release, features, dependencies, downloads, owners, readme, compare, health, audit, alternatives, dep_tree, audit_mix_deps, upgrade_check, docs, search_docs, doc_item.
No error handling guidance visible. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next. No recovery guides or error classification.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |
List the curated projects in an Elixir Toolbox category.
List the categories in a single Elixir Toolbox group.
Browse the Elixir Toolbox curated taxonomy of groups and categories.
Search packages via Elixir Toolbox. Results carry GitHub/GitLab stats, popularity, and health signals not exposed by the raw hex.pm search.
List trending Elixir packages from Elixir Toolbox.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields without knowing what each tool returns. No evidence of return type documentation.
No pagination parameters visible for tools that likely return lists (search, versions, dependencies, docs, search_docs, toolbox_search). Large result sets risk context window exhaustion.
Tool names 'readme', 'features', 'health' are ambiguous. 'readme' does not start with a verb (get_, fetch_, retrieve_). 'features' and 'health' lack clarity on what resource they operate on (package features? system health?).