This is a boilerplate/template project, not a functional MCP server. The 16 tools are declared in scripts/verify-mcp.mjs but NO input schemas, parameter descriptions, or output schemas are visible in the source code. Tool definitions appear to be inferred from nodebench-mcp (a dependency), not explicitly defined here. The src/index.ts contains only a trivial hello() function. Without access to the actual tool registration code and schemas, per-tool scores are capped at 50 per the rubric. Most tools lack any visible description beyond their names. This is a starter template, not a production-ready server.

• Add explicit tool registration with full JSON Schema input definitions for all 16 tools. Include type, description, and constraints for every parameter.
• Write 50 - 200 character descriptions for each tool explaining WHAT it does, WHEN to use it, and any prerequisites. Example: 'bootstrap_project: Register this project with NodeBench verification system. Call this first to initialize quality gates and enable verification cycles.'
• Add parameter descriptions for all inputs. For example, if 'run_quality_gate' accepts a 'gate_name' parameter, describe it: 'The name of the quality gate preset to execute (e.g., core, full, starter).'
• Document output schemas for each tool. Specify what fields are returned, their types, and what IDs/references are included for chaining downstream calls.
• Standardize tool naming to verb_noun snake_case convention. Rename 'getMethodology' → 'get_methodology' and clarify vague names like 'manipulate_screenshot' and 'run_mandatory_flywheel' to specific actions.