From umbraco-mcp-skills
Count MCP tools in an SDK-based project and analyze implementation gaps against .discover.json. Use when the user asks about tool counts, progress, or collection coverage.
npx claudepluginhub umbraco/umbraco-mcp-base --plugin umbraco-mcp-skillsThis skill is limited to using the following tools:
This skill counts all MCP tools in the project and provides a detailed breakdown by collection. When a `.discover.json` manifest exists, it also performs gap analysis showing which collections have tools, integration tests, and eval tests.
Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.
Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.
Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.
This skill counts all MCP tools in the project and provides a detailed breakdown by collection. When a .discover.json manifest exists, it also performs gap analysis showing which collections have tools, integration tests, and eval tests.
Use this skill when:
npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/count-mcp-tools/scripts/count-tools.ts
To also show all tool names in the console output:
SHOW_TOOLS=true npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/count-mcp-tools/scripts/count-tools.ts
To save results to a markdown file:
OUTPUT_FILE=docs/analysis/api-endpoints-analysis.md npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/count-mcp-tools/scripts/count-tools.ts
| Variable | Description | Default |
|---|---|---|
TOOLS_DIR | Path to the tools directory (relative to PROJECT_ROOT) | src/umbraco-api/tools |
OUTPUT_FILE | Optional path to save markdown analysis report | (none) |
SHOW_TOOLS | Set to true to show individual tool names in console output | false |
PROJECT_ROOT | Root of the consumer project | . |
EVALS_DIR | Path to eval tests directory (relative to PROJECT_ROOT) | tests/evals |
API_GENERATED_DIR | Path to generated API client files (relative to PROJECT_ROOT) | src/umbraco-api/api/generated |
When a .discover.json file exists in the project root, the script automatically compares expected collections against actual implementation:
Gap Analysis (.discover.json):
================================================================================
Collection | Tools | Endpoints | Tests | Evals | Status
--------------------------------------------------------------------------------
form | 12 | 12/20 | yes | yes | Complete
form-template | 6 | 6/8 | yes | no | Missing evals
field-type | 0 | 0/5 | no | no | Not started
folder | 4 | 4/4 | yes | yes | Complete
================================================================================
2/4 collections complete | 22/37 endpoints covered (59%)
For each collection listed in .discover.json, it checks:
{TOOLS_DIR}/{collection}/__tests__/*.test.ts?{EVALS_DIR}/*{collection}*.test.ts?The counting script is at scripts/count-tools.ts and counts TypeScript files that define actual MCP tools (containing ToolDefinition and withStandardDecorators), excluding index.ts, test files, and helper/utility files.