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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_shots"
  }
}

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026
- addedOutput schema / properties / shots / items / properties / machine_settings / additionalProperties
```
Added value: +true
```
- changedOutput schema / properties / shots / items / properties / machine_settings / type
```
Previous value: -[
-  "null",
-  "string"
-]New value: +[
+  "object",
+  "null"
+]
```

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / shots / items / properties / machine_settings
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```

changedOutput schema / properties / shots / items / required

Previous value: -[
-  "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",
-  "bag_id",
-  "bean_name",
-  "taste_pending"
-]New value: +[
+  "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",
+  "bag_id",
+  "machine_settings",
+  "bean_name",
+  "taste_pending"
+]

Changed12 schema fields changedSep 28, 2026
- removedOutput schema / properties / shots / items / properties / beverage_g / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / bloom_time_s / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / ey_pct / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / first_drip_time_s / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / program_id / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / rating / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / tds / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / temperature_c / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / verdict / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / vessel_name / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / vessel_weight_g / type
```
Removed value: -"null"
```
- removedOutput schema / properties / shots / items / properties / water_id / type
```
Removed value: -"null"
```
Changed1 schema field changedSep 16, 2026
- changedOutput schema / properties / shots / items / properties / flavor_notes / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed3 schema fields changedSep 12, 2026

addedInput schema / properties / filters / properties / bag_id

Added value: +{
+  "description": "Filter by bag number (one purchase of a coffee)",
+  "type": "integer"
+}

addedOutput schema / properties / shots / items / properties / bag_id
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / properties / shots / items / required

Previous value: -[
-  "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"
-]New value: +[
+  "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",
+  "bag_id",
+  "bean_name",
+  "taste_pending"
+]

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent read, so the description correctly spends its words elsewhere: it discloses that taste_pending is a derived flag and defines precisely what makes it 1. It does not state default sort order or whether filtering combines with AND, which are meaningful behavioral details for a list tool.

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?

Two sentences, front-loaded with capability and then the derived-field explanation. The taste_pending parenthetical is dense but every clause adds information an agent cannot get from the name alone; 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, the description needn't explain return values, and annotations cover the safety profile. What remains thin is ordering and filter-composition behavior, but the core call-correctly information is present.

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 coverage is 67%, so the schema already carries most parameter meaning, including a taste_pending definition nearly identical to the description's. The description adds the actionable consequence (backfill via update_shot) but says nothing about how limit/offset behave at boundaries or how multiple filters compose. Baseline 3 fits.

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 and resource ("List shot history") plus the two capabilities that matter (pagination, filtering). It does not distinguish itself from neighbors like get_stats or diagnose_shot, but the resource is concrete enough that an agent can identify the tool's job.

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 clear context for use (history retrieval with pagination/filtering) and explicitly names update_shot as the path for backfilling an owed tasting, which is real routing guidance. No exclusion rules tell the agent when to prefer get_stats or diagnose_shot instead, keeping it below a 5.

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?