Loading ToolBench
A context package manager (CTXPM) CLI tool for managing project dependencies, packages, skills, rules, specs, prompts, and MCP resources. Provides commands for initialization, installation, validation, updates, and migration of context resources.
Bear.CTXPM is a CLI tool for managing context and project metadata. While all 12 tools have descriptions and input schemas are visible, the quality is inconsistent. Tool names lack clear verb-noun structure (e.g., 'entrypoint doctor' is vague; 'validate_entrypoint' would be clearer). Descriptions are present but often generic (e.g., 'Manage project memory and context state' for 'memory' tool). Parameter descriptions exist but lack specificity on constraints, formats, and valid ranges. Output schemas are not documented in the source. Error handling guidance is absent. The 'memory' tool has a vague input schema ('type: object') with no field definitions. Most tools support --dry-run and --json flags, but these are not consistently documented as parameters in the schema. No tool declares permissions, security implications, or idempotency guarantees.
Add a new resource (skill, rule, spec, prompt, mcp, memory) from a source URL to the project
Check for available updates to dependencies and packages
Detect agent profiles and check enrollment status
Diagnose and validate the project entrypoint configuration
Initialize a ctxpm project with manifest, entrypoints, and directory structure
Install or repair all resources (dependencies and packages) in the project
List all resources (dependencies and packages) in the project, optionally filtered by type or kind
Tool 'memory' has vague input schema ('type: object') with no field definitions, violating constrained-input pattern. LLM cannot determine valid subcommands or parameters.
Tool 'entrypoint doctor' uses non-standard naming ('entrypoint' + 'doctor' as subcommand). Should be 'validate_entrypoint' or 'diagnose_entrypoint' to follow verb_noun convention.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., resource IDs for chaining). Violates response-shaper and tool-chain patterns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
Manage project memory and context state
Migrate legacy resource configurations to the current manifest format
Remove a resource from the project manifest and filesystem
Update dependencies and packages to available newer versions
Validate the project manifest and resource configuration
Parameter descriptions lack specificity on constraints. E.g., 'agent' param in init/detect has no enum of valid agent profiles. 'type' param in add/list lacks enum of valid resource types (skill|rule|spec|prompt|mcp|memory).
No error handling guidance in descriptions. Tools like 'remove' (DESTRUCTIVE) and 'install' (WRITE) lack recovery hints or confirmation patterns. Violates recovery-guide and confirmation-request patterns.