count-mcp-tools
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.
What this skill does
# Count MCP 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.
## When to Use
Use this skill when:
- User asks "how many tools do we have?"
- User wants statistics about tool collections
- User needs to know tool distribution across collections
- User asks about project progress or coverage
- User wants to evaluate skill/agent completion status
- User asks which collections still need tests or evals
## Instructions
1. Run the counting script from the consumer project root:
```bash
npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/count-mcp-tools/scripts/count-tools.ts
```
To also show all tool names in the console output:
```bash
SHOW_TOOLS=true npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/count-mcp-tools/scripts/count-tools.ts
```
To save results to a markdown file:
```bash
OUTPUT_FILE=docs/analysis/api-endpoints-analysis.md npx tsx ${CLAUDE_PLUGIN_ROOT}/skills/count-mcp-tools/scripts/count-tools.ts
```
2. Present results showing:
- Total tool count
- Breakdown by collection (sorted alphabetically)
- List of individual tool names per collection (when SHOW_TOOLS=true or in markdown output)
- Gap analysis table (when .discover.json exists)
- If OUTPUT_FILE is set, saves to markdown file with full tool listing
## Environment Variables
| 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` |
## Gap Analysis
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**: Does the collection directory exist with tool files? (count > 0)
- **Tests**: Are there integration test files in `{TOOLS_DIR}/{collection}/__tests__/*.test.ts`?
- **Evals**: Are there eval test files matching `{EVALS_DIR}/*{collection}*.test.ts`?
## Supporting Files
The counting script is at [scripts/count-tools.ts](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.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.