Skip to main content
Glama

tarn_scaffold

Generate a minimal .tarn.yaml skeleton from OpenAPI operation, curl, method+URL, or a recorded fixture. Returns YAML with metadata and optionally writes to disk.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curlNoPayload for mode=curl. Provide either `command` (inline) or `file` (path to read).
cwdNoAbsolute path to the project root. Defaults to the workspace root captured during MCP `initialize`, or the server process's current directory.
explicitNoPayload for mode=explicit.
forceNoAllow overwriting an existing `out` path.
formatNoWhen `out` is set, write YAML (default) or the JSON metadata block.
modeYesInput mode. Must match the payload object provided.
nameNoOverride the inferred top-level `name:` field.
openapiNoPayload for mode=openapi.
outNoWrite the scaffold to this path (relative paths resolve against `cwd`). Refuses to overwrite unless `force=true`.
recordedNoPayload for mode=recorded.
Behavior3/5

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

Without annotations, the description carries full burden. It discloses core behavior (generating skeleton, returning metadata, optional file write) but omits details about side effects, permissions, or safety considerations. The `force` and `out` overwrite behavior is described in the schema but not reiterated.

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?

The description is extremely concise—three sentences covering all key aspects without redundancy. It prioritizes the main action, input modes, output, and optional file writing.

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 the lack of output schema and the tool's complexity (10 params, nested objects), the description provides a good overview of inputs and outputs (YAML + structured metadata). However, it could be more explicit about the exact return format or fields.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by summarizing input modes and providing an equivalent CLI command, but does not deepen understanding beyond what the schema already conveys.

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's purpose: generating a minimal `.tarn.yaml` skeleton from four distinct input modes. It specifies the output (rendered YAML plus structured metadata) and optional file writing, distinguishing it from other tools on the server.

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

Usage Guidelines4/5

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

The description implicitly guides when to use the tool by enumerating the four input modes (OpenAPI, curl, explicit, recorded). However, it does not explicitly state when not to use it or mention alternatives, leaving some ambiguity for the agent.

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