ShotPulled

Update a shot

update_shot

DestructiveIdempotent

Correct fields on an already-logged shot in place, with no need to delete and re-log. Use for fixing a wrong dose/yield/time or grind label, re-filing a shot onto the right bean (bean_id), backfilling rating/tasting notes, or fixing the timestamp (pulled_at). Changing grind_label re-derives the numeric grind position from the shot's grinder; changing yield/time/dose/tds keeps flow rate and extraction yield consistent automatically.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	Yes	Only the fields to change
`shot_id`	Yes	ID of the shot to correct

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`shot_id`	Yes
`updated_fields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / fields / properties / machine_settings

Added value: +{
+  "description": "The machine's selector positions for this shot, {key: position}; replaces what was stamped, null clears it",
+  "maxProperties": 16,
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed2 schema fields changedSep 12, 2026

addedInput schema / properties / fields / properties / bag_id

Added value: +{
+  "description": "Re-file the shot onto this bag; must be a bag of the shot's bean",
+  "type": "integer"
+}

changedInput schema / properties / fields / properties / bean_id / description

Previous value: -"Re-file the shot onto this bean"New value: +"Re-file the shot onto this bean (its current bag, unless bag_id is also given)"

First observedSep 6, 2026

TDQS

Score is being calculated.

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?