Loading ToolBench
Provides Typescript type definitions for NPM packages
Single tool 'npm-types' has a basic description but lacks parameter descriptions entirely. Input schema uses Zod validation (name, version as strings) but provides no type hints or constraints in the schema itself. No output schema is documented. Error handling returns raw error messages without recovery guidance. The tool description (16 chars) is below the 20-char minimum threshold. No parameter descriptions exist, violating the 100% baseline for A+ tools. Tool does one thing (fetch types) but lacks the metadata and guidance needed for reliable LLM invocation.
Fetches the types for an NPM package
Tool description is only 16 characters ('Fetches the types for an NPM package'), below 20-char minimum. Lacks WHEN to use it, prerequisites, or what it returns. LLMs cannot determine selection criteria.
No parameter descriptions. 'name' and 'version' parameters lack any guidance on format, constraints, or examples. LLMs cannot infer whether 'version' accepts 'latest', '1.0.0', or ranges like '^1.0.0'.
No output schema documented. Tool returns text content but LLMs have no visibility into structure, fields, or what to expect. Prevents downstream tool chaining and forces parsing guesswork.
Error handling returns raw error messages ('No types found for this package', 'No body found') without recovery guidance. LLMs cannot determine if error is retryable, user-fixable, or fatal.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2026-07-28+ | v2 |
Tool name 'npm-types' does not start with action verb. Should be 'get_npm_types' or 'fetch_npm_types' to signal intent. Current name is noun-based and ambiguous.