ShotPulled

Update a shot

update_shot

Idempotent

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.

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so safety is covered. The description adds non-obvious derived-value behavior: grind_label re-derives the numeric grind position and yield/time/dose/tds keep flow rate and extraction yield consistent automatically. It stops short of permission or failure-mode disclosure, so not 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.

Conciseness5/5

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

Two dense sentences, front-loaded with the core action and the reason to prefer it over delete/re-log, then the concrete use cases and side effects. No filler.

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 and annotations covering safety, the description covers the key gap: the in-place correction semantics and the automatic re-derivation side effects. It fully equips an agent to call it, with only minor omission of error/permission behavior.

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 the schema already documents bean_id, bag_id, tasted, data_confidence, etc. The description's parameter references (dose/yield/time, grind_label, bean_id, pulled_at) largely restate schema text, so baseline 3 is appropriate.

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 and resource ('Correct fields on an already-logged shot in place') and immediately distinguishes itself from delete_shot/log_shot by noting no delete/re-log is needed. An agent can tell it apart from the 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 Guidelines4/5

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

Gives a concrete list of when-to-use cases (fix wrong dose/yield/time, re-file onto a bean, backfill rating/notes, fix timestamp) and rules out the delete-and-re-log alternative. It does not explicitly name delete_shot or log_shot as alternatives, but the context is unambiguous.

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?