ShotPulled

Set calibration offset

set_maintenance_offset

DestructiveIdempotent

Record how far a maintenance job moved the reference, on an entry that opened a calibration epoch. Takes an ENTRY, not a piece of equipment: the offset belongs to the event that caused it, which is what lets several of them compose for a recipe locked before all of them. Zero is a legitimate measurement and means "measured, and it had not moved". Omit offset_value entirely to clear it back to unmeasured.

Input Schema

Name	Required	Description
`source`	No	How it was arrived at: pull, counted, or typed
`entry_id`	Yes	The maintenance entry that opened the epoch, from list_grinders
`evidence`	No	One line recording what it rested on, e.g. "Reference pull 1.38 g/s against 1.74 g/s locked."
`offset_value`	No	Clicks to ADD to a pre-clean reading to get the same grind today, signed along the collar's own number direction. 0 records "unchanged"; omit to clear the measurement

Output Schema

Name	Required	Description	Default
`entry`	Yes
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026
- removedOutput schema / properties / entry / properties / details / properties / to / properties / components_spec / type
```
Removed value: -"null"
```
- removedOutput schema / properties / entry / properties / guide_id / type
```
Removed value: -"null"
```

Changed2 schema fields changedSep 27, 2026

addedOutput schema / properties / entry / properties / guide_id
```
Added value: +{
+  "type": "null"
+}
```

changedOutput schema / properties / entry / required

Previous value: -[
-  "id",
-  "equipment_kind",
-  "equipment_id",
-  "task",
-  "performed_at",
-  "disturbs_zero",
-  "note",
-  "offset_value",
-  "offset_source",
-  "offset_at",
-  "evidence",
-  "details",
-  "details_version",
-  "created_at",
-  "details_known"
-]New value: +[
+  "id",
+  "equipment_kind",
+  "equipment_id",
+  "task",
+  "performed_at",
+  "disturbs_zero",
+  "note",
+  "offset_value",
+  "offset_source",
+  "offset_at",
+  "evidence",
+  "details",
+  "details_version",
+  "created_at",
+  "guide_id",
+  "details_known"
+]

Changed7 schema fields changedSep 16, 2026

addedOutput schema / properties / entry / properties / details / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / entry / properties / details / properties

Added value: +{
+  "from": {
+    "additionalProperties": true,
+    "properties": {
+      "components_spec": {
+        "type": "string"
+      },
+      "nominal_step": {
+        "type": "integer"
+      },
+      "setting_scheme": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "setting_scheme",
+      "nominal_step",
+      "components_spec"
+    ],
+    "type": "object"
+  },
+  "to": {
+    "additionalProperties": true,
+    "properties": {
+      "components_spec": {
+        "type": "null"
+      },
+      "nominal_step": {
+        "type": "number"
+      },
+      "setting_scheme": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "setting_scheme",
+      "nominal_step",
+      "components_spec"
+    ],
+    "type": "object"
+  }
+}

addedOutput schema / properties / entry / properties / details / required
```
Added value: +[]
```
changedOutput schema / properties / entry / properties / details / type
```
Previous value: -"null"New value: +[
+  "null",
+  "object"
+]
```
addedOutput schema / properties / entry / properties / details_known
```
Added value: +{
+  "type": "boolean"
+}
```
changedOutput schema / properties / entry / properties / evidence / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / entry / required

Previous value: -[
-  "id",
-  "equipment_kind",
-  "equipment_id",
-  "task",
-  "performed_at",
-  "disturbs_zero",
-  "note",
-  "offset_value",
-  "offset_source",
-  "offset_at",
-  "evidence",
-  "details",
-  "details_version",
-  "created_at"
-]New value: +[
+  "id",
+  "equipment_kind",
+  "equipment_id",
+  "task",
+  "performed_at",
+  "disturbs_zero",
+  "note",
+  "offset_value",
+  "offset_source",
+  "offset_at",
+  "evidence",
+  "details",
+  "details_version",
+  "created_at",
+  "details_known"
+]

AddedAug 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

It provides significant behavioral detail beyond the structured fields by defining the logical meaning of 0 (unchanged), the semantic implication of omitting offset_value (clearing measurement), and the relational context (offsets composing for a locked recipe). These details add substantial clarity.

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 prose is highly technical yet perfectly structured. Every sentence contributes vital, specific information (e.g., 'Zero is a legitimate measurement,' 'takes an ENTRY') and the flow is logical and dense.

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?

The description provides a comprehensive context for a highly technical tool. By explaining concepts like 'calibration epoch' and the dependency on the entry ID, it ensures the AI agent has the full necessary context for correct invocation.

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?

With 100% schema description coverage, the baseline is 3. The description elevates this by explaining the 'signed direction' of the offset and the context of the 'entry,' adding crucial meaning that transcends the formal type definitions.

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 is highly specific, stating that it records how a maintenance job moved the reference and attaches this data to the entry that opened a calibration epoch. This clearly defines the tool's domain within the overall system architecture.

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?

While it clarifies that the offset belongs to an 'ENTRY, not a piece of equipment,' which provides crucial scope guidance, it does not explicitly suggest alternatives like 'log_maintenance,' making it an implied usage scenario rather than a direct comparison.

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

All ShotPulled tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?