tarn-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tarn_runA | Run API tests defined in .tarn.yaml files. Writes artifacts under .tarn/runs/<run_id>/ and returns a compact agent report by default plus paths to the full artifacts so agents do not need to keep large JSON blobs in context. |
| tarn_validateA | Validate .tarn.yaml test files without executing them. Checks YAML syntax and schema validity. |
| tarn_listA | List all available tests in .tarn.yaml files. Returns file names, test names, and step counts. |
| tarn_fix_planA | Analyze a Tarn JSON report and return a prioritized fix plan with next actions, evidence, and remediation hints. Accepts either a |
| tarn_last_failuresA | Return the grouped failures (NAZ-402) for a specific run as structured JSON. Reads the persisted |
| tarn_get_run_artifactsA | Return artifact paths plus existence flags for a specific run. Does not load any artifact payload — just tells the agent what is on disk for the given run. |
| tarn_rerun_failedA | Rerun only the failing |
| tarn_reportA | Render the concise report (NAZ-404) for a persisted run: a tiny JSON envelope with totals, exit code, and grouped failures. No HTTP, no test execution — purely reads |
| tarn_inspectA | Inspect a prior run's archived report (NAZ-405) at run, file, test, or step granularity. Optional |
| tarn_impactA | Map a change (files / endpoints / openapi ops / |
| tarn_scaffoldA | Generate a minimal |
| tarn_run_agentA | Run a suite with |
| tarn_last_root_causesA | Return only the root-cause failure groups (NAZ-402) for a run, without the wider failures envelope. The fastest failures-first read for an agent planning a fix. Equivalent to: tarn failures --format json (groups only). |
| tarn_pack_contextA | Assemble a remediation bundle (NAZ-414) from a prior run's artifacts: failing entries enriched with YAML snippets, request/response excerpts, captures lineage, and rerun hints. Supports truncation budgets for context-limited agents. Equivalent to: tarn pack-context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Tools are largely distinct, but tarn_run and tarn_run_agent overlap in purpose despite differing modes, and tarn_last_failures/tarn_last_root_causes/tarn_report have subtle granularity differences that could cause minor confusion.
All tools follow a consistent tarn_verb_noun or tarn_noun pattern in snake_case, making the set predictable and easy to navigate.
14 tools cover the full lifecycle of testing with Tarn without being excessive; each tool serves a clear, non-redundant role.
The tool surface includes running tests, inspecting results in multiple granularities, impact analysis, scaffolding, validation, and fix planning—leaving no obvious gaps for the domain.