Skip to main content
Glama
Keesan12

MartinLoop — Stop Runaway Loops, Bad Code & Token Waste

by Keesan12
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Local

martin_pause

Destructive

Pause a MartinLoop run by writing a durable receipt before risky follow-up work. Choose the run via file, loopId, or latest; add reason and requestedBy for audit context.

Instructions

Write a durable pause receipt for one canonical MartinLoop run. Provide exactly one selector: file, loopId, or latest; runsDir changes the run-store root, while reason and requestedBy add audit context. Use for a temporary hold before risky follow-up work. This records a request and does not kill a process; use martin_cancel to abandon work or martin_continue to resume.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoPath to one canonical run record or directory. Mutually exclusive with loopId and latest.
latestNoWhen true, targets the latest canonical run. Mutually exclusive with file and loopId.
loopIdNoCanonical MartinLoop run identifier. Mutually exclusive with file and latest.
reasonNoOptional non-empty reason recorded in the pause receipt.
runsDirNoOptional run-store root override used to resolve loopId or latest.
requestedByNoOptional human or runtime identity label recorded for audit context.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe control action that was recorded.
loopIdYesMartinLoop run identifier the control was applied to.
reasonNoHuman-readable reason for the control, if provided.
controlIdYesUnique receipt ID for this control action.
requestedAtYesISO 8601 timestamp when the control was recorded.
requestedByNoIdentity that requested the control, if provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.6
    • removedInput schema / oneOf
      Removed value: -[
-  {
-    "required": [
-      "file"
-    ]
-  },
-  {
-    "required": [
-      "loopId"
-    ]
-  },
-  {
-    "required": [
-      "latest"
-    ]
-  }
-]
  2. Changed6 schema fields changedv0.5.9
    • addedInput schema / properties / file / description
      Added value: +"Path to one canonical run record or directory. Mutually exclusive with loopId and latest."
    • addedInput schema / properties / latest / description
      Added value: +"When true, targets the latest canonical run. Mutually exclusive with file and loopId."
    • addedInput schema / properties / loopId / description
      Added value: +"Canonical MartinLoop run identifier. Mutually exclusive with file and latest."
    • addedInput schema / properties / reason / description
      Added value: +"Optional non-empty reason recorded in the pause receipt."
    • addedInput schema / properties / requestedBy / description
      Added value: +"Optional human or runtime identity label recorded for audit context."
    • addedInput schema / properties / runsDir / description
      Added value: +"Optional run-store root override used to resolve loopId or latest."
  3. Changed3 schema fields changedv0.5.6
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedOutput schema / properties
      Added value: +{
+  "action": {
+    "description": "The control action that was recorded.",
+    "enum": [
+      "pause",
+      "cancel",
+      "continue"
+    ],
+    "type": "string"
+  },
+  "controlId": {
+    "description": "Unique receipt ID for this control action.",
+    "type": "string"
+  },
+  "loopId": {
+    "description": "MartinLoop run identifier the control was applied to.",
+    "type": "string"
+  },
+  "reason": {
+    "description": "Human-readable reason for the control, if provided.",
+    "type": "string"
+  },
+  "requestedAt": {
+    "description": "ISO 8601 timestamp when the control was recorded.",
+    "type": "string"
+  },
+  "requestedBy": {
+    "description": "Identity that requested the control, if provided.",
+    "type": "string"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "loopId",
+  "action",
+  "controlId",
+  "requestedAt"
+]
  4. First observedv0.3.9

TDQS

A4.7/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the annotations: it clarifies that the tool 'records a request' and 'does not kill a process,' which tempers the destructiveHint and prevents the agent from expecting process termination. It also conveys durability and audit-context behavior. It does not fully explain what side effects the destructiveHint refers to, but it does not contradict the 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?

The description is compact and front-loaded: purpose first, then the central selection constraint, then the usage context, then behavioral clarification and sibling routing. Every sentence contributes information; there is no filler or redundant repetition of the schema.

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?

With six parameters, a one-of selection requirement, an output schema, and many sibling tools, the description is sufficient for an agent to call the tool correctly. It covers the selection constraint, the effect of each parameter group, the appropriate use case, and how this tool differs from cancel/continue. The output schema removes the need to describe return values.

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 schema already documents each parameter. The description adds value by grouping parameters into functional roles: selectors (file/loopId/latest), run-store override (runsDir), and audit context (reason/requestedBy). It also communicates the critical 'exactly one selector' rule, which the schema only fragments through mutual-exclusion notes.

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: 'Write a durable pause receipt for one canonical MartinLoop run.' It immediately distinguishes this tool from cancel/continue by defining the artifact it produces, and the 'exactly one selector' constraint sharpens the operational intent. No ambiguity about what the tool is for.

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?

It explicitly states when to use the tool: 'for a temporary hold before risky follow-up work.' It also gives direct routing guidance by naming martin_cancel and martin_continue as alternatives for abandoning or resuming work, so an agent can choose between siblings without guessing.

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