Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 report object from tarn_run or the same inputs as tarn_run to execute first.

tarn_last_failuresA

Return the grouped failures (NAZ-402) for a specific run as structured JSON. Reads the persisted failures.json rather than re-running the tests. Useful for agents that want a failures-only view without loading the full report.

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 (file, test) pairs from a prior run. Response shape matches tarn_run (run_id, artifacts, report) so agents can loop run → inspect → rerun without switching tool surfaces.

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 summary.json + failures.json.

tarn_inspectA

Inspect a prior run's archived report (NAZ-405) at run, file, test, or step granularity. Optional filter_category narrows the view to one FailureCategory. Response includes artifact paths for the run that seeded the view.

tarn_impactA

Map a change (files / endpoints / openapi ops / git diff) to the .tarn.yaml tests it most likely affects, with confidence tiers and run hints. Read-only: no HTTP and no test execution. Equivalent to: tarn impact --format json.

tarn_scaffoldA

Generate a minimal .tarn.yaml skeleton from one of four input modes (OpenAPI operation id, raw curl, method+url, or a recorded fixture). Returns the rendered YAML plus structured metadata (TODOs, inferred request, validation). Optional out writes the file to disk. Equivalent to: tarn scaffold --from-openapi / --from-curl / --method+--url / --from-recorded.

tarn_run_agentA

Run a suite with report_mode=agent pre-selected, surfacing the compact AgentReport (NAZ-412) plus artifact paths. Preferred entry point when the caller will iterate on failures. Equivalent to: tarn run --agent.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 14 tools

Disambiguation4/5

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.

Naming Consistency5/5

All tools follow a consistent tarn_verb_noun or tarn_noun pattern in snake_case, making the set predictable and easy to navigate.

Tool Count5/5

14 tools cover the full lifecycle of testing with Tarn without being excessive; each tool serves a clear, non-redundant role.

Completeness5/5

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.

Maintenance

ActivityInactive
ResponsivenessSlow