Skip to main content
Glama
Tarmac MCP

Tarmac MCP

Official
by tarmacagent

Attach to an existing run

tarmac_attach

Connect an MCP agent to an existing Tarmac app run using its run ID and run credential to continue or inspect that run.

Instructions

Attach to a run created in the Tarmac app (Run → Your agent) using its run id and run credential.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "runId": "<runId>",
      "runToken": "<runToken>"
    },
    "name": "tarmac_attach"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYes
runTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It does not say whether attaching establishes an exclusive session, whether the call is idempotent, how long the attachment lasts, or whether the token is a secret that must be protected.

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?

One front-loaded sentence with no filler; the disambiguating details (Tarmac app, Run → Your agent) come early. Nothing is bloated, though it is under-specified rather than concise in the positive sense.

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

Completeness2/5

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

With no annotations and no output schema, the description must explain what the agent gets back from attaching and what it is expected to do next. Neither is covered, leaving the agent unable to predict the result of a successful call.

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

Parameters2/5

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

Schema description coverage is 0%: the schema only carries regex patterns, with no prose for either parameter. The description contributes just the loose phrases "run id" and "run credential" for runId and runToken, without explaining where the credential comes from or that it must match the trt_ prefix.

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

Purpose4/5

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

Specific verb (attach) plus resource (a run) plus the source of the identifier, which separates it from tarmac_start_run and tarmac_get_run. It stops short of naming a sibling explicitly, so differentiation is inferential rather than stated.

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?

Gives context for where the run comes from ("Run → Your agent" in the Tarmac app) and implies use after a run already exists. It never states prerequisites, whether attaching must precede other calls, or what to do when the run is finished or already attached.

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