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

TableJSON 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

TableJSON 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

A3.9/5.0

Behavior4/5

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

Annotations already declare write (readOnlyHint false), destructiveHint true, and idempotentHint true. The description adds non-obvious behavioral context beyond that: zero is a legitimate recorded measurement distinct from omission, and omission clears the measurement back to unmeasured — which is exactly the destructive-ish overwrite an agent needs to understand before calling. No auth or rate-limit notes, so short of a 5.

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?

Purpose and scope are front-loaded in the first clause, and each sentence carries information. The middle sentence about offsets composing 'for a recipe locked before all of them' is somewhat dense/indirect, costing a point.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and annotations plus the 100%-covered schema carry most of the load. The description supplies the key domain caveats (entry-scoping, zero vs omission), leaving only explicit sibling routing as a minor gap.

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 all four parameters are already documented in the schema, including the zero/omit semantics of offset_value. The description largely reframes rather than extends that (entry_id as 'the event that caused it', which enables composition), so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb+resource: recording the calibration offset a maintenance job introduced, keyed to the epoch-opening entry. It also distinguishes scope from equipment-oriented siblings with 'Takes an ENTRY, not a piece of equipment.' Clear, though the prose is abstract enough that an agent must read a full sentence to extract the verb.

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

Usage Guidelines4/5

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

It establishes the condition of applicability (an entry that opened a calibration epoch) and gives a concrete mode-selection rule: zero to record 'unchanged', omit offset_value to clear back to unmeasured. The 'entry, not equipment' line implicitly routes away from set_grinder_position, but no sibling tool is named explicitly and there is no explicit when-not.

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?