Skip to main content
Glama
Tarmac MCP

Tarmac MCP

Official
by tarmacagent

Get the run record

tarmac_get_run
Read-only

Retrieve the active run's status, verdict, reason, and balance changes to review policy-checked swap outcomes and trace results.

Instructions

Status, verdict, reason and balance changes for the active run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tarmac_get_run"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read with no side effects, so the bar is lower. The description adds the useful constraint that it reports on the "active" run, implying behavior when no run is active, but it does not say whether that case errors or returns empty — a notable gap for a status-check call.

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?

A single compact sentence with no filler, and the most important field (status) is listed first. As a fragment without a leading verb it reads slightly like a field list rather than a capability statement, but nothing is wasted.

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?

With no output schema, the description does a reasonable job of naming the returned fields, which is exactly the right compensation. It still leaves open what happens without an active run, and it doesn't clarify how the reported balance changes differ from tarmac_get_balances — details an agent would want before calling.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. The description's mention of "active run" correctly signals that the target is implicit rather than passed in.

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

Purpose3/5

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

The description enumerates what the run record contains (status, verdict, reason, balance changes) and scopes it to "the active run", so the resource is identifiable. However, it is a noun phrase with no verb — the retrieval action only comes from the name and title — and it never explicitly states it returns a record rather than performing an action.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no comparison to siblings such as tarmac_get_balances or tarmac_get_context, which could plausibly overlap on balance information. The agent must infer that this is the tool to call after tarmac_start_run to inspect progress.

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