AgentXM

ShotPulled

mcp remote · streamable-http · v1.4.2 · source: crawl

https://mcp.shotpulled.com/mcp

Espresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks.

AgentXM badge

Works

100

Verified Oct 31, 2026 · p50 646 ms · p95 666 ms

Worth

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Checks

CheckWeightResultEvidence
reachable20pass3 of 3 handshakes succeeded; server 'shotpulled'
tools_listed15pass44 tools
schema_complete15pass44 of 44 tools have a description and a typed schema
latency_p5010passp50 646 ms
latency_p955passp95 666 ms
error_free10pass0 of 3 attempts failed
auth_posture10passhttps, open
injection_scan10passno patterns found
scope5passno execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Tools (44)

NameDescriptionSchema
list_watersList registered waters for the account. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back.typed
kb_changelogRetrieve the changelog showing updates and version differences for the knowledge base.typed
register_grinderRegister a manual or electric grinder with its dial settings scheme. It becomes the active grinder only when no grinder is in use (none active, or the active one archived); otherwise call set_active wtyped
set_grinder_positionSet the current grinder collar position. source="measured" resets verification freshness. It replaces the stored position; no history of earlier positions is kept.typed
register_machineRegister an espresso or alternative preparation machine. It becomes the active machine only when no machine is in use (none active, or the active one archived); otherwise call set_active with its machtyped
set_equipment_archivedArchive or restore a grinder, machine, water, or scale.typed
update_grinderCorrect a registered grinder: its name, burrs, collar scheme, nominal step, layout, range or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also typed
update_machineCorrect a registered machine (its name, control type, prep type and style, basket, boiler, accessories or notes), or record where its selectors stand (settings). Only the keys you send in fields changtyped
register_waterRegister a custom or commercial water formulation.typed
update_scaleCorrect a registered scale: its type, resolution, capacity, capabilities, build or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a ttyped
update_waterCorrect a registered water: its name, type, mineral figures or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field, but not atyped
log_maintenanceLog a cleaning or maintenance job against a piece of equipment. A task that takes the thing apart opens a calibration epoch, and every recipe locked before it is read through that epoch's offset. Recotyped
set_maintenance_offsetRecord how far a maintenance job moved the reference, on an entry that opened a calibration epoch. Takes an ENTRY, not a piece of equipment: the offset belongs to the event that caused it, which is whtyped
set_maintenance_scheduleSet the user's own schedule for one maintenance task on one grinder or machine: their own interval, switching it off, or muting the reminder until a date. Only the keys you send in fields change; sendtyped
get_maintenance_guidesStep-by-step maintenance guides: tools, supplies, steps and warnings, in our own words with the maker's documents as sources. With no arguments, every guide for the user's current grinders and machinetyped
list_maintenance_dueWhat maintenance is due across the user's current grinders and machines, most urgent first. Use it for "is anything due?". Only tasks with an interval compete: a task the machine counts and signals ittyped
register_scaleRegister a brewing scale: the instrument that weighs the dose and the yield.typed
list_scalesList registered scales for the account. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back.typed
register_programRegister a programmed shot button on a machine. A program cuts the shot off either by weight (program_type "volumetric", set target_volume_g) or by time (program_type "timed", set target_time_s). One typed
register_coffeeRegister a coffee that is NOT yet in list_beans, together with its first bag. It does not switch a coffee in use: it becomes active only when no coffee is in use (none active, or the active one archivtyped
set_activeSwitch the active bean, grinder or machine for this account. The numbers come from list_beans, list_grinders and list_machines. Registering a coffee, grinder or machine makes it active only when nothityped
update_beanUpdate a coffee's own fields (roaster, origins, roast level, rest window, notes, rating…). Bag-shaped fields sent here (state, roast_date, bag_weight_g, grams_remaining, cost…) land on the coffee's CUtyped
get_dial_stateRetrieve current dialing state, active context, recent shots, recommendations, and locked recipes.typed
log_shotLog an espresso or alternative shot/brew attempt. Uses the active context (bean/grinder/machine/program) unless overridden via bean_id/grinder_id/machine_id/program_id. ALWAYS pass bean_id explicitly typed
lock_recipeLock a successful shot as the reference dialing recipe for this equipment profile. It overwrites the recipe already locked for the same coffee, grinder, machine, program and drink intent, which keeps typed
delete_shotDelete a logged shot from history. Restores the bean's remaining weight (which is derived from logged doses). Hard delete: there is no undo. To fix a mistake on an otherwise-valid shot, prefer update_typed
update_shotCorrect 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), backfillingtyped
list_recipesList recipes (all or filtered by equipment and status). The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back.typed
get_statsGet compact flat usage stats for a grinder, machine, or bean.typed
list_grindersList grinders registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back. Eactyped
list_machinesList machines registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back. Eactyped
list_beansList the coffees registered for the account, with status filter. Each coffee carries its bags[] (every purchase, with its own freshness and grams left) and current_bag_id; the row's top-level roast_datyped
grinder_mathDetermine steps/clicks difference and directions between setting labels (C3).typed
compute_ageCompute a bag's age in days off roast and its resting/staling verdict, for the coffee's current bag by default or for the bag named.typed
diagnose_shotEvaluate shot metrics to provide ranked hypotheses (C6) and warn on flip-flops (G2) or fatigue (G6). Resolves the SHOT's own bean (age computed at the shot's pulled_at), never the active profile, and typed
suggest_next_stepRetrieve the single next experiment step from the reasoning engine.typed
log_recommendationLog a recommended dialing change to allow contradiction/oscillation checking (G2).typed
get_ruleRetrieve the detailed text of a specific rule from the knowledge base by its rule ID.typed
get_kb_versionRetrieve the current version of the knowledge base.typed
diagnose_previewSandbox-only diagnosis, writes nothing (no verdict, no recommendation-trail entry). Two modes: pass shot_id to dry-run a LOGGED shot (optionally overriding its sensory_tags, for the "what would this rtyped
list_shotsList 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 typed
register_bagRegister another bag of a coffee that is already in list_beans: the same roaster's product, bought again. It keeps the coffee's recipes, notes and history; only the purchase facts (roast date, weight,typed
update_bagChange bag-level facts on one bag of a coffee: open, seal, freeze, thaw or finish it, correct its roast date, weight, grams left or price. Bag numbers come from the bags[] on list_beans (or current_batyped
merge_beansFold one coffee into another when the same coffee was registered twice. Every bag, shot, recipe and recommendation of from_bean_id moves to into_bean_id; the active coffee follows if it was the one metyped

Badge

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/com-shotpulled-shotpulled.svg)](https://app.agent-xm.com/a/com-shotpulled-shotpulled)

Was this agent useful?

Claim this listing

The token was returned when the agent was registered. No token? Prove the domain or repository instead.