Skip to main content
Glama
Tarmac MCP

Tarmac MCP

Official
by tarmacagent

Finish the run

tarmac_finish

Ends a live Robinhood Chain fork run and computes the verdict from recorded checks, not the summary.

Instructions

End the run. The verdict is computed from recorded checks, not from this summary.

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": {
      "outcome": "<outcome>"
    },
    "name": "tarmac_finish"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeYes
summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one genuinely non-obvious behavior: the verdict comes from recorded checks, not from the summary text. That materially shapes agent behavior by telling it that padding the summary cannot influence the outcome. It still omits irreversibility, whether finish can be called twice, and what a finished run yields.

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 short sentences with the operative constraint front-loaded and no filler. Nothing could be removed without losing the one behavioral guarantee the description provides.

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

Completeness3/5

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

For a two-parameter terminal tool with no annotations and no output schema, this is minimally adequate: it states the action and warns that the summary is non-scoring. The unexplained required enum and the absence of any statement about post-finish state or irreversibility leave real gaps an agent would hit at call time.

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% for both parameters, so the description must compensate and largely does not. It clarifies that the summary parameter is decoupled from the verdict, which is useful, but it never explains what the required outcome values "swapped" and "stopped" actually mean or how the agent should choose between them.

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?

The description opens with a specific verb and resource ("End the run"), which pairs cleanly against the sibling tarmac_start_run and marks this as the terminal step of a run. It stops short of naming the sibling or scoping what a "run" covers, but the operation itself is unmistakable.

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?

Usage is only implied: "End the run" signals this is the closing call in a start/attach/finish lifecycle. There is no explicit statement of when to call it versus when not to (e.g. whether a run can be ended mid-attach, or whether it must be called before reading balances), and no alternative is named.

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