Skip to main content
Glama
Keesan12

MartinLoop — Stop Runaway Loops, Bad Code & Token Waste

by Keesan12
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Local

martin_dossier

Read-onlyIdempotent

Retrieve a formatted evidence summary for one MartinLoop run to confirm verification results, costs, and changes before merge or release claims. Output as JSON, Markdown, or GitHub PR format.

Instructions

Read a formatted evidence summary for one MartinLoop run. Provide exactly one selector: file, loopId, or latest; runsDir changes the run-store root. Set format to json, md, or github-pr; json is the default. Use after martin_run, before merge or release claims, or when sharing what happened. Do not use as a substitute for missing verifier evidence; use martin_run_dossier for the full structured record. Next: review verification results, retry, or hand off the receipt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoPath to one run record or directory. Mutually exclusive with loopId and latest.
formatNoOutput format. Defaults to json.
latestNoWhen true, loads the latest run. Mutually exclusive with file and loopId.
loopIdNoMartinLoop run identifier. Mutually exclusive with file and latest.
runsDirNoOptional run-store root override used to resolve loopId or latest.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
costYes
loopYes
budgetYes
sourceYes
relatedYes
attemptsYes
warningsYes
artifactsYes
inspectionYes
sourceKindYes
recentEventsYes
verificationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.9
    • addedInput schema / properties / file / description
      Added value: +"Path to one run record or directory. Mutually exclusive with loopId and latest."
    • addedInput schema / properties / format / description
      Added value: +"Output format. Defaults to json."
    • addedInput schema / properties / latest / description
      Added value: +"When true, loads the latest run. Mutually exclusive with file and loopId."
    • addedInput schema / properties / loopId / description
      Added value: +"MartinLoop run identifier. Mutually exclusive with file and latest."
    • addedInput schema / properties / runsDir / description
      Added value: +"Optional run-store root override used to resolve loopId or latest."
  2. Changed2 schema fields changedv0.5.6
    • 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"
+]
  3. Changed2 schema fields changedv0.5.5
    • 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"
+]
  4. Changed4 schema fields changedv0.5.3
    • 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"
+]
  5. First observedv0.3.9

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description's 'Read' is consistent. It adds useful behavioral context: the summary is formatted, a selector must be supplied, format defaults to json, and the output is meant to serve as a handoff receipt. This goes beyond the annotations without contradicting them.

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?

The description is compact and front-loaded with the core purpose, followed by parameter rules, usage context, and alternatives. The 'Next: review verification results, retry, or hand off the receipt' sentence is slightly vague but adds workflow context without bloating the text.

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 5-parameter read-only tool with 100% schema coverage, an output schema, and readOnly/idempotent annotations, the description covers everything needed: what it reads, how to select a run, format handling, runsDir override, workflow timing, and the sibling alternative. No critical operational detail is missing.

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 description coverage is 100%, so the schema already fully documents file, loopId, latest, format, and runsDir. The description repeats the selector exclusivity and the format options rather than adding new semantic depth. This meets the baseline but does not substantially elevate parameter understanding.

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 opens with a specific verb and resource: 'Read a formatted evidence summary for one MartinLoop run.' It also clearly distinguishes itself from the sibling martin_run_dossier by calling that the 'full structured record,' so an agent can select between them without inspecting schemas.

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?

The description gives explicit when-to-use guidance: 'Use after martin_run, before merge or release claims, or when sharing what happened.' It also provides an explicit exclusion: 'Do not use as a substitute for missing verifier evidence; use martin_run_dossier for the full structured record.' This is strong routing guidance.

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

Deploy Server

Other Tools