ShotPulled

Update a shot

update_shot

DestructiveIdempotent

Correct fields on an already-logged shot in place — 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)"

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "shot_id": {
+      "type": "integer"
+    },
+    "status": {
+      "type": "string"
+    },
+    "updated_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "status",
+    "shot_id",
+    "updated_fields",
+    "message"
+  ],
+  "type": "object"
+}

Changed9 schema fields changedJul 19, 2026

addedInput schema / properties / fields / properties / data_confidence / description

Added value: +"estimated marks the metrics as a best guess instead of burying the caveat in notes"

changedInput schema / properties / fields / properties / data_confidence / enum

Previous value: -[
-  "measured",
-  "recalled"
-]New value: +[
+  "measured",
+  "recalled",
+  "estimated"
+]

addedInput schema / properties / fields / properties / flavor_notes / description
```
Added value: +"null clears the notes"
```
changedInput schema / properties / fields / properties / flavor_notes / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
addedInput schema / properties / fields / properties / rating / description
```
Added value: +"1-5; null clears the rating"
```

changedInput schema / properties / fields / properties / rating / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

addedInput schema / properties / fields / properties / tasted

Added value: +{
+  "description": "Backfill 1 to mark a pending shot as tasted-clean (tasted, no defect tags) so it leaves the taste-pending queue without inventing a tag or rating",
+  "enum": [
+    0,
+    1
+  ],
+  "type": "integer"
+}

addedInput schema / properties / fields / properties / verdict / description
```
Added value: +"null clears the verdict"
```
changedInput schema / properties / fields / properties / verdict / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

AddedJul 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare mutation/destructive/idempotent traits, and the description adds behavior beyond them: changing grind_label re-derives the numeric grind position, and changing yield/time/dose/tds keeps flow rate and extraction yield consistent automatically. These cascading side effects are exactly the non-obvious behavior an agent needs and cannot get from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core operation, then use cases, then side effects—each sentence carries distinct information. Slightly dense, but no sentence is disposable.

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 an output schema present, return values needn't be described, and with 100% schema coverage the field list is covered. The description supplies the cascading-behavior context a correct invocation depends on, leaving nothing material missing.

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 baseline is 3, but the description adds cross-field semantics: bean_id re-filing and the automatic re-derivation triggered by grind_label vs the consistency-keeping of yield/time/dose/tds. This goes beyond the per-field schema text without fully restating every parameter.

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?

States a specific verb+resource ('Correct fields on an already-logged shot in place') and immediately distinguishes itself from the delete-and-re-log workflow. An agent can tell it apart from sibling delete_shot and log_shot without opening a schema.

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?

Enumerates concrete when-to-use cases: fixing a wrong dose/yield/time or grind label, re-filing onto the right bean, backfilling rating/tasting notes, or correcting the timestamp. The 'no need to delete and re-log' clause routes the agent away from delete_shot, functioning as an explicit alternative.

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?