> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-in-ai/17.latest/mcp/base-mcp/sdk/coverage-tracking.md).

# Coverage Tracking

As your MCP server grows, you need to know which API operations have tools and which are deliberately excluded. The Claude Code plugin provides two skills for this.

## Counting Tools

The `/count-mcp-tools` skill counts tools per collection and displays a summary. Use it to track implementation progress and identify collections with too many or too few tools.

```
/count-mcp-tools
```

## Cataloging Ignored Endpoints

The `/update-ignored-endpoints` skill analyzes your generated API clients and compares them against implemented tools. Endpoints that are not implemented are cataloged in `docs/analysis/IGNORED_ENDPOINTS.md` with coverage statistics and categorization.

```
/update-ignored-endpoints
```

This produces:

* Total endpoint count and coverage percentage
* Categorized list of ignored endpoints grouped by collection
* Reasons for exclusion (security, deprecation, unsuitable for MCP)

Maintaining this file gives you a clear record of which API endpoints are deliberately excluded and why. The `/discuss-mcp` skill respects this file and will not suggest building tools for ignored endpoints.

## When to Run

Run these skills whenever you add or remove tools, or after running `/build-tools` to generate new collections. Keeping coverage data up to date helps you make informed decisions about what to implement next.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-in-ai/17.latest/mcp/base-mcp/sdk/coverage-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.