ShotPulled

List shots

list_shots

Read-onlyIdempotent

List shot history with support for pagination and filtering. Every shot carries a derived taste_pending flag (1 = logged with no sensory tags, no rating, and no tasted flip — the tasting is still owed and can be backfilled with update_shot).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of records to return (1-500)
`offset`	No	Offset for pagination
`filters`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`shots`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 27, 2026

addedOutput schema / properties / shots / items

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "bean_id": {
+      "type": "integer"
+    },
+    "bean_name": {
+      "type": "string"
+    },
+    "best_brew": {
+      "type": "integer"
+    },
+    "beverage_g": {
+      "type": "null"
+    },
+    "bloom_time_s": {
+      "type": "null"
+    },
+    "data_confidence": {
+      "type": "string"
+    },
+    "dose_g": {
+      "type": "integer"
+    },
+    "drink_intent": {
+      "type": "string"
+    },
+    "ey_pct": {
+      "type": "null"
+    },
+    "favourite": {
+      "type": "integer"
+    },
+    "finish_action": {
+      "type": "string"
+    },
+    "first_drip_time_s": {
+      "type": "null"
+    },
+    "flavor_notes": {
+      "type": "string"
+    },
+    "flow_rate_gps": {
+      "type": "number"
+    },
+    "grind_components": {
+      "type": "string"
+    },
+    "grind_label": {
+      "type": "string"
+    },
+    "grind_position_value": {
+      "type": "integer"
+    },
+    "grinder_id": {
+      "type": "integer"
+    },
+    "id": {
+      "type": "integer"
+    },
+    "machine_id": {
+      "type": "integer"
+    },
+    "observations": {
+      "type": "string"
+    },
+    "program_id": {
+      "type": "null"
+    },
+    "pulled_at": {
+      "type": "string"
+    },
+    "rating": {
+      "type": "null"
+    },
+    "sensory_tags": {
+      "type": "string"
+    },
+    "taste_pending": {
+      "type": "integer"
+    },
+    "tasted": {
+      "type": "integer"
+    },
+    "tds": {
+      "type": "null"
+    },
+    "temp_taste": {
+      "type": "string"
+    },
+    "temperature_c": {
+      "type": "null"
+    },
+    "time_s": {
+      "type": "integer"
+    },
+    "verdict": {
+      "type": "null"
+    },
+    "vessel_name": {
+      "type": "null"
+    },
+    "vessel_weight_g": {
+      "type": "null"
+    },
+    "water_id": {
+      "type": "null"
+    },
+    "yield_g": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "pulled_at",
+    "bean_id",
+    "grinder_id",
+    "machine_id",
+    "program_id",
+    "grind_label",
+    "grind_components",
+    "grind_position_value",
+    "dose_g",
+    "yield_g",
+    "time_s",
+    "flow_rate_gps",
+    "finish_action",
+    "drink_intent",
+    "flavor_notes",
+    "sensory_tags",
+    "observations",
+    "temp_taste",
+    "rating",
+    "verdict",
+    "data_confidence",
+    "temperature_c",
+    "bloom_time_s",
+    "first_drip_time_s",
+    "beverage_g",
+    "tds",
+    "ey_pct",
+    "water_id",
+    "vessel_name",
+    "vessel_weight_g",
+    "favourite",
+    "best_brew",
+    "tasted",
+    "bean_name",
+    "taste_pending"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "shots": {
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "shots",
+    "total"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 19, 2026

addedInput schema / properties / filters / properties / taste_pending

Added value: +{
+  "description": "1 = shots logged without sensory tags, a rating, or the tasted flip (tasting still owed); 0 = tasted shots",
+  "enum": [
+    0,
+    1
+  ],
+  "type": "integer"
+}

First observedJun 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this operation read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by explaining the derived taste_pending flag's exact condition and pointing to update_shot for backfilling, which goes beyond what annotations provide.

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 sentences, each earning its place: the first states the core purpose and capabilities, the second explains a non-obvious derived flag. Purpose is front-loaded and there is no repetition of schema details.

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?

Given the output schema exists and annotations cover safety, the description is largely complete: it explains pagination, filtering, and the meaning of the important derived flag. It could more explicitly state that the taste_pending filter can be combined with other filters to find owed tastings, but that is implicitly clear.

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?

The schema already documents limit, offset, and the filters and their ranges/enums. The description's taste_pending explanation largely mirrors the schema's own filter description, though it does add the backfill pointer. With 67% schema coverage, the description provides moderate added value but doesn't compensate heavily for the undocumented filters wrapper.

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 states a specific action and resource: 'List shot history'. It also mentions the two key capabilities (pagination and filtering), which clearly differentiates it from sibling list_* tools and from mutation tools like update_shot.

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?

The description makes obvious when list_shots is appropriate: to retrieve shot history with pagination/filtering. It also references update_shot as the follow-up for backfilling owed tastings, giving useful workflow context. However, it does not explicitly state when not to use this tool or compare it with an 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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation4/5

Most tools target a clearly distinct resource and action, and the list/register/update/set tool families are easy to tell apart. The closest pair is diagnose_preview and diagnose_shot, which are well-described but similar enough in name that an agent could select the wrong one.

Naming Consistency4/5

The overwhelming majority of tools follow a consistent verb_noun pattern (list_beans, register_grinder, update_shot, set_active). Minor exceptions like grinder_math and kb_changelog lack the imperative verb prefix, but they are readable and do not create real confusion.

Tool Count2/5

34 tools is above the 25+ threshold and feels heavy even though the domain is fairly rich. The many parallel list_* and register_* tools for beans, grinders, machines, scales, waters, programs, and recipes could plausibly be consolidated or trimmed without losing core capability.

Completeness3/5

The core shot lifecycle is well covered: log, update, delete, diagnose, and list shots, plus bean registration and maintenance tracking. However, most registered entities lack update/delete tools, and get_rule has no corresponding list_rules tool, leaving some obvious workflow gaps that agents must work around.

Resources

Need Help?