test-inventory-mcp

Overview Schema Source Related Servers Discussions Admin

Test summary

test_summary

Read-onlyIdempotent

Counts tests by state, tag, or annotation from test files without running them, with optional grouping by file or tag. Use it to answer how many tests are skipped or where.

Instructions

Counts a project's tests by state (active, skip, fixme, todo, expectedToFail, notLoaded) and by tag and annotation, from the test files, without running them. Use it first, for questions such as how many tests are skipped, or which files or tags have the most skipped tests; use find_tests to list the tests themselves. states, tags and grep count only the tests they match. groupBy "file" or "tag" adds the counts of each file or tag, sorted by name and paged with limit and cursor; a test with no tag is in no tag group. Example: {"states": ["skip", "fixme"], "groupBy": "file"}.

Input Schema

TableJSON Schema

Name	Required	Description
`grep`	No	Keeps tests whose fullName (describe titles and title joined with " > ") matches this regular expression, ignoring case.
`tags`	No	Keeps tests with one of these tags, written as in the titles, such as "@smoke".
`limit`	No	The most items to return.
`cursor`	No	nextCursor from the previous answer, for the next page. Keep the other arguments the same.
`states`	No	Keeps tests in one of these states.
`groupBy`	No	Adds the counts of each file or each tag.
`patterns`	No	Globs of the test files, relative to `directory`, such as ["tests/*/.spec.ts"]. Default: the ones the server was started with.
`directory`	No	A folder inside the project to scan, relative to its root, such as "packages/web". Default: the root.
`framework`	No	The test runner. Default: the one the server was started with.

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	Yes
`total`	Yes
`groups`	Yes
`summary`	Yes	Counts over the matching tests; fileCount is every file scanned.
`framework`	Yes
`nextCursor`	Yes
`scanErrors`	Yes	Problems of level error in the scan, which may leave tests out of the answer.
`frameworkVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavior: counting happens 'without running them', filters are conjunctive ('states, tags and grep count only the tests they match'), grouping is sorted by name and paged, and untagged tests fall into no tag group.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the primary use case, then semantics, then an example. Dense but nearly every clause carries information; only the example and the tag-edge-case sentence push it toward run-on length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained. For a 9-parameter, zero-required aggregation tool the description covers counting semantics, filter conjunction, grouping, pagination and the alternative tool, leaving no significant gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema: it explains what groupBy does (adds per-file/per-tag counts, sorted by name, paged), that cursor paging requires keeping other arguments the same, and the no-tag edge case. That is genuine added meaning over the field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Counts a project's tests by state... and by tag and annotation, from the test files, without running them') and scopes the source of truth. It also names find_tests as the sibling that lists tests, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: 'Use it first, for questions such as how many tests are skipped, or which files or tags have the most skipped tests; use find_tests to list the tests themselves.' Both the when-to-use and the when-to-use-something-else are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server