MartinLoop — Stop Runaway Loops, Bad Code & Token Waste

martin_run_dossier

Read-onlyIdempotent

Read the full execution record for a single run, covering attempts, events, artifacts, verification, integrity, and cost. Use when comprehensive evidence review is required.

Instructions

Read the full structured execution dossier for one MartinLoop run, including attempts, events, artifacts, verification, integrity, cost, and related discovery surfaces. Provide exactly one selector: file, loopId, or latest; runsDir changes the run-store root. Use for comprehensive evidence review. Do not use for a compact state check; use martin_get_run, or use martin_dossier when formatted sharing output is required.

Input Schema

TableJSON Schema

Name	Required	Description
`file`	No	Path to a canonical loop-record.json, legacy file, or run-store directory. Mutually exclusive with loopId and latest.
`latest`	No	When true, loads the most recently updated loop record. Mutually exclusive with file and loopId.
`loopId`	No	Loop ID under the run store. Mutually exclusive with file and latest.
`runsDir`	No	Optional run-store root override used to resolve loopId or latest.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cost`	Yes
`loop`	Yes
`budget`	Yes
`source`	Yes
`related`	Yes
`attempts`	Yes
`warnings`	Yes
`artifacts`	Yes
`inspection`	Yes
`sourceKind`	Yes
`recentEvents`	Yes
`verification`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.9Sep 2, 2026

changedInput schema / properties / file / description

Previous value: -"Path to a canonical loop-record.json, legacy file, or run-store directory."New value: +"Path to a canonical loop-record.json, legacy file, or run-store directory. Mutually exclusive with loopId and latest."

changedInput schema / properties / latest / description

Previous value: -"When true, loads the most recently updated loop record in the run store."New value: +"When true, loads the most recently updated loop record. Mutually exclusive with file and loopId."

changedInput schema / properties / loopId / description

Previous value: -"Loop ID under the run store."New value: +"Loop ID under the run store. Mutually exclusive with file and latest."

changedInput schema / properties / runsDir / description

Previous value: -"Optional runs-root override."New value: +"Optional run-store root override used to resolve loopId or latest."

Changed2 schema fields changedv0.5.6Aug 30, 2026

changedOutput schema / properties / budget / required

Previous value: -[
-  "maxUsd",
-  "softLimitUsd",
-  "maxIterations",
-  "maxTokens"
-]New value: +[
+  "maxUsd",
+  "softLimitUsd",
+  "maxIterations"
+]

changedOutput schema / properties / loop / required

Previous value: -[
-  "loopId",
-  "title",
-  "objective",
-  "status",
-  "lifecycleState",
-  "attempts",
-  "costUsd",
-  "avoidedUsd",
-  "pressure",
-  "shouldStop",
-  "remainingBudgetUsd",
-  "remainingIterations",
-  "remainingTokens"
-]New value: +[
+  "loopId",
+  "title",
+  "objective",
+  "status",
+  "lifecycleState",
+  "attempts",
+  "costUsd",
+  "avoidedUsd",
+  "pressure",
+  "shouldStop",
+  "remainingBudgetUsd",
+  "remainingIterations"
+]

Changed2 schema fields changedv0.5.5Aug 23, 2026

removedOutput schema / properties / loop / properties / costProvenance

Removed value: -{
-  "enum": [
-    "actual",
-    "calculated",
-    "estimated",
-    "unavailable"
-  ],
-  "type": "string"
-}

changedOutput schema / properties / loop / required

Previous value: -[
-  "loopId",
-  "title",
-  "objective",
-  "status",
-  "lifecycleState",
-  "attempts",
-  "costUsd",
-  "costProvenance",
-  "avoidedUsd",
-  "pressure",
-  "shouldStop",
-  "remainingBudgetUsd",
-  "remainingIterations",
-  "remainingTokens"
-]New value: +[
+  "loopId",
+  "title",
+  "objective",
+  "status",
+  "lifecycleState",
+  "attempts",
+  "costUsd",
+  "avoidedUsd",
+  "pressure",
+  "shouldStop",
+  "remainingBudgetUsd",
+  "remainingIterations",
+  "remainingTokens"
+]

Changed4 schema fields changedv0.5.3Aug 19, 2026

addedOutput schema / properties / cost / properties / provenance

Added value: +{
+  "enum": [
+    "actual",
+    "calculated",
+    "estimated",
+    "unavailable"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / cost / required

Previous value: -[
-  "actualUsd",
-  "avoidedUsd",
-  "tokensIn",
-  "tokensOut"
-]New value: +[
+  "actualUsd",
+  "avoidedUsd",
+  "tokensIn",
+  "tokensOut",
+  "provenance"
+]

addedOutput schema / properties / loop / properties / costProvenance

Added value: +{
+  "enum": [
+    "actual",
+    "calculated",
+    "estimated",
+    "unavailable"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / loop / required

Previous value: -[
-  "loopId",
-  "title",
-  "objective",
-  "status",
-  "lifecycleState",
-  "attempts",
-  "costUsd",
-  "avoidedUsd",
-  "pressure",
-  "shouldStop",
-  "remainingBudgetUsd",
-  "remainingIterations",
-  "remainingTokens"
-]New value: +[
+  "loopId",
+  "title",
+  "objective",
+  "status",
+  "lifecycleState",
+  "attempts",
+  "costUsd",
+  "costProvenance",
+  "avoidedUsd",
+  "pressure",
+  "shouldStop",
+  "remainingBudgetUsd",
+  "remainingIterations",
+  "remainingTokens"
+]

First observedv0.3.9Jul 29, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds meaningful behavioral context by specifying that the tool reads a full dossier, requires exactly one selector, that runsDir changes the run-store root, and that it is not a formatted-output tool. No contradiction with annotations.

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?

Three purposeful sentences with no filler. The main purpose is front-loaded, followed by selector usage and then exclusion guidance. Every sentence contributes actionable information.

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

Completeness5/5

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

For a read-only, idempotent tool with full schema coverage and an output schema, the description is complete. It covers purpose, selector constraints, runsDir semantics, and alternative tools, leaving no critical calling decision ambiguous.

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?

Schema coverage is 100%, so the baseline is already 3. The description goes beyond the schema by stating the exclusivity requirement ('exactly one selector') and clarifying runsDir's role ('changes the run-store root'), adding value on top of the already well-described parameters.

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?

Uses a specific verb ('Read') with a clearly defined resource: 'the full structured execution dossier for one MartinLoop run.' It enumerates the dossier contents (attempts, events, artifacts, verification, integrity, cost, discovery surfaces) and explicitly contrasts itself with martin_get_run and martin_dossier, making sibling differentiation easy.

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

Usage Guidelines5/5

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

States exactly when to use it ('comprehensive evidence review') and when not to ('compact state check'), naming the alternatives explicitly: martin_get_run for compact state and martin_dossier for formatted sharing output. It also gives selector usage guidance ('exactly one selector: file, loopId, or latest').

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

martin_run_dossier

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools