Skip to main content
Glama

tarn_run

Run API tests from .tarn.yaml files and get a compact agent report with artifact paths.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoAbsolute path to the project root. tarn.config.yaml, tarn.env.yaml, and relative paths are resolved against this directory. Defaults to the workspace root captured during MCP `initialize`, or the server process's current directory.
envNoEnvironment name (loads tarn.env.{name}.yaml)
pathNoPath to a .tarn.yaml test file or directory containing test files. Relative paths resolve against `cwd`.
report_modeNoWhich slice of the run to return inline. `agent` (default) is the compact root-cause-first payload; `summary` and `failures` return the NAZ-401 artifacts; `full` returns the verbose JSON report. The run still writes every artifact regardless of the chosen mode.
tagNoFilter tests by tag (comma-separated)
varsNoVariable overrides as key-value pairs
Behavior3/5

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

The description discloses side effects (writes artifacts under .tarn/runs/<run_id>/) and behavior (returns compact agent report by default, avoids large JSON blobs). With no annotations, this partially covers safety and operational context, but missing details on permissions, rate limits, or idempotency.

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

Conciseness5/5

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

Two sentences with no wasted words; front-loaded with core action and key behavioral notes. Efficient and clear.

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

Completeness4/5

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

Given no output schema, the description explains the return format (compact agent report + artifact paths) and covers the key parameters. It could elaborate on error handling or the structure of the agent report, but for a run tool with sibling helpers, it's adequately complete.

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?

All parameters are described in the input schema (100% coverage). The description adds value by explaining the default report mode ('agent'), the behavior of artifact writing regardless of mode, and the default resolution of 'cwd'. It clarifies semantics beyond the schema's 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?

The description clearly states the tool runs API tests from .tarn.yaml files, which distinguishes it from sibling tools like tarn_validate (validation) and tarn_list (listing). The verb 'Run' and resource 'API tests defined in .tarn.yaml files' specify the exact action.

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

Usage Guidelines3/5

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

The description implies the tool is for executing tests but does not explicitly state when to use it over alternatives. It does not provide criteria for selection, such as 'use for full test execution; use tarn_validate for configuration checks'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NazarKalytiuk/tarn'

If you have feedback or need assistance with the MCP directory API, please join our Discord server