Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.armature.tech/llms.txt

Use this file to discover all available pages before exploring further.

The coverage report gives you a clear picture of which tools in your MCP server’s catalog are being actively exercised — and which ones your workflows have never touched. Tools that go untested are invisible to Armature’s health checks, which means regressions in those tools won’t be caught until a user or a downstream system notices. The coverage report exists to surface those gaps so you can write the missing workflows.

​
How coverage is calculated

Armature calculates coverage from two sources:
  1. Actual tool calls in workflow runs. If a workflow run successfully invokes a tool, that tool is counted as covered. Armature looks at the most recent 50 runs for the server and considers at most 100 active tools when computing the report.
  2. Explicit allowed_tools policies. If a workflow’s configuration includes an allowed_tools list, the tools named in that list are counted as covered even if no run has called them yet — the policy expresses intent to use those tools.
An open-policy workflow — one with no allowed_tools restriction — does not count as covering all tools. Coverage requires either a successful tool call in a run or an explicit entry in an allowed_tools policy. Wildcards and unrestricted workflows do not contribute to coverage.

​
Read the coverage report

The coverage report is available directly from the server detail page:
  1. Go to MCP Servers and click on any server card to open the detail panel.
  2. Click the Coverage tab.
The report splits your server’s tool catalog into two groups:
GroupMeaning
CoveredTools that appear in at least one recent workflow run or are listed in an allowed_tools policy.
UncoveredTools that have never been called in any of the last 50 runs and are not named in any allowed_tools policy.
Each covered tool shows which workflows have called it, making it easy to trace coverage back to specific workflow definitions.

​
Access coverage via the MCP API

If you are using the Armature MCP repair API, the coverage report is also available as a machine-readable resource: 
armature://mcp-servers/{id}/coverage-report
Replace {id} with your MCP server’s identifier. Fetch this resource in an agent session to get a structured view of covered and uncovered tools that you can use when drafting new workflows or regression suites.
Coverage reports use fixed defaults: the most recent 50 runs for the server and at most 100 active tools. Resource URIs do not accept query string parameters to change these limits.
See the MCP API resources reference for the full resource schema and how to authenticate.

​
Close coverage gaps

When you find uncovered tools, the next step is to write workflows that exercise them. A well-targeted workflow gives Armature a way to verify the tool’s behavior on every run and provides a baseline for the repair loop to compare against.
You can use the design_workflow_suite prompt in the Armature MCP API to ask an AI agent to read your coverage report and propose new workflow definitions for uncovered tools automatically.
Use the coverage gaps view to prioritize which tools to target first. A good heuristic:
  • High-risk tools (payment processing, data mutations, external API calls) should be covered first even if they are called infrequently.
  • Core path tools that most of your users depend on should have coverage before peripheral or administrative tools.
  • Untested tools that have no monitor and no workflow coverage represent a complete blind spot — consider adding both a tool monitor and a workflow.
See authoring workflows for a step-by-step guide to creating a new workflow targeting a specific tool.

Connect an MCP server

Add a server so Armature can discover its tools and track coverage.

Authoring workflows

Write a workflow that targets uncovered tools and closes your coverage gaps.

Tool monitors

Add per-tool health checks that run on a schedule independently of workflows.

MCP API resources

Fetch the coverage report programmatically from an agent session.