Skip to main content
Glama
Sign In

ShotPulled

by com.shotpulled.mcp
OverviewDiscussionsAdmin

Log maintenance

log_maintenance

Log 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. Record the offset here if you counted the clicks while reassembling, which is the one moment anybody actually knows it. Any task in the maintenance vocabulary can be logged against a grinder or machine it belongs to, including one the maker advises against, because the log records what was done. Read each piece of equipment's tasks, their intervals and their due state from list_grinders and list_machines.

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: what you did, and anything that surprised you
taskYesWhich maintenance job was performed
detailsNoFields specific to this task. Which ones a task takes is published as details_fields on each task; a burr clean takes none
evidenceNoOne line recording what the measurement rested on, e.g. "Counted 6 clicks coarser at reassembly."
guide_idNoOptional: the id of the maintenance guide that was followed. Must be a guide for this task
equipment_idYesThe ID of that piece of equipment
offset_valueNoThe correction, if you measured it now: clicks to ADD to a pre-clean reading to get the same grind today, signed along the collar's own number direction. Omit it and the epoch stays unmeasured, which is a state the app shows rather than a zero it assumes
performed_atNoWhen it was done (ISO 8601 or YYYY-MM-DD HH:MM:SS, UTC). Defaults to now; backdating is fine
disturbs_zeroNoWhether this job disturbed the reference the stored numbers are read against: for a burr clean, whether the burrs actually came out. Defaults to the task's own answer; send 0 for a wipe-down that left the collar alone
offset_sourceNoHow the offset was arrived at: pull (a reference shot), counted (clicks counted at reassembly), typed (asserted directly)
equipment_kindYesWhich kind of equipment this job was done on

Output Schema

NameRequiredDescriptionDefault
entryYes
dedupedYes
messageYes
entry_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / disturbs_zero / description
      Previous value: -"Whether this job disturbed the reference the stored numbers are read against — for a burr clean, whether the burrs actually came out. Defaults to the task's own answer; send 0 for a wipe-down that left the collar alone"New value: +"Whether this job disturbed the reference the stored numbers are read against: for a burr clean, whether the burrs actually came out. Defaults to the task's own answer; send 0 for a wipe-down that left the collar alone"
    • changedInput schema / properties / guide_id / description
      Previous value: -"Optional — the id of the maintenance guide that was followed. Must be a guide for this task"New value: +"Optional: the id of the maintenance guide that was followed. Must be a guide for this task"
    • changedInput schema / properties / note / description
      Previous value: -"Optional — what you did, and anything that surprised you"New value: +"Optional: what you did, and anything that surprised you"
  2. Changed12 schema fields changed
    • changedInput schema / properties / details / description
      Previous value: -"Fields specific to this task. Which ones a task takes is published as details_fields in the task catalog on list_grinders; a burr clean takes none"New value: +"Fields specific to this task. Which ones a task takes is published as details_fields on each task; a burr clean takes none"
    • changedInput schema / properties / equipment_kind / enum
      Previous value: -[
-  "grinder"
-]New value: +[
+  "grinder",
+  "machine"
+]
    • addedInput schema / properties / guide_id
      Added value: +{
+  "description": "Optional — the id of the maintenance guide that was followed. Must be a guide for this task",
+  "type": "string"
+}
    • changedInput schema / properties / task / enum
      Previous value: -[
-  "burr_clean"
-]New value: +[
+  "burr_clean",
+  "backflush_water",
+  "backflush_detergent",
+  "descale",
+  "group_gasket_replace",
+  "shower_screen_clean",
+  "shower_screen_replace",
+  "group_head_wipe",
+  "basket_portafilter_soak",
+  "steam_wand_purge",
+  "steam_wand_soak",
+  "drip_tray_clean",
+  "water_tank_clean",
+  "water_filter_replace",
+  "boiler_water_change",
+  "lever_piston_seal_replace",
+  "lever_lubricate",
+  "milk_system_clean",
+  "professional_service",
+  "builtin_grinder_burr_clean",
+  "builtin_grinder_burr_replace",
+  "grinder_quick_clean",
+  "grinder_cleaning_tablets",
+  "burr_replace",
+  "hopper_clean",
+  "grounds_cup_clean",
+  "bearing_lubricate",
+  "gasket_seal_replace",
+  "idle_rinse",
+  "water_wash",
+  "dishwasher",
+  "filter_prime",
+  "softener_regenerate",
+  "other"
+]
    • addedOutput schema / properties / deduped
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / entry / properties / details / additionalProperties
      Added value: +true
    • addedOutput schema / properties / entry / properties / details / properties
      Added value: +{
+  "filter_id": {
+    "type": "string"
+  },
+  "label": {
+    "type": "string"
+  },
+  "product": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / entry / properties / details / required
      Added value: +[]
    • changedOutput schema / properties / entry / properties / details / type
      Previous value: -"null"New value: +[
+  "null",
+  "object"
+]
    • addedOutput schema / properties / entry / properties / guide_id
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • changedOutput schema / properties / entry / required
      Previous value: -[
-  "id",
-  "equipment_kind",
-  "equipment_id",
-  "task",
-  "performed_at",
-  "disturbs_zero",
-  "note",
-  "offset_value",
-  "offset_source",
-  "offset_at",
-  "evidence",
-  "details",
-  "details_version",
-  "created_at",
-  "details_known"
-]New value: +[
+  "id",
+  "equipment_kind",
+  "equipment_id",
+  "task",
+  "performed_at",
+  "disturbs_zero",
+  "note",
+  "offset_value",
+  "offset_source",
+  "offset_at",
+  "evidence",
+  "details",
+  "details_version",
+  "created_at",
+  "guide_id",
+  "details_known"
+]
    • changedOutput schema / required
      Previous value: -[
-  "entry_id",
-  "entry",
-  "message"
-]New value: +[
+  "entry_id",
+  "entry",
+  "deduped",
+  "message"
+]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / entry / properties / details_known
      Added value: +{
+  "type": "boolean"
+}
    • changedOutput schema / properties / entry / required
      Previous value: -[
-  "id",
-  "equipment_kind",
-  "equipment_id",
-  "task",
-  "performed_at",
-  "disturbs_zero",
-  "note",
-  "offset_value",
-  "offset_source",
-  "offset_at",
-  "evidence",
-  "details",
-  "details_version",
-  "created_at"
-]New value: +[
+  "id",
+  "equipment_kind",
+  "equipment_id",
+  "task",
+  "performed_at",
+  "disturbs_zero",
+  "note",
+  "offset_value",
+  "offset_source",
+  "offset_at",
+  "evidence",
+  "details",
+  "details_version",
+  "created_at",
+  "details_known"
+]
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: a disassembly task opens a calibration epoch, prior locked recipes are reinterpreted through that epoch's offset, and omitting offset_value leaves the epoch visibly unmeasured rather than assumed zero. These are consequential side effects not derivable from readOnly=false/destructive=false.

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?

Purpose and epoch consequence are front-loaded and almost every sentence carries information. A few asides ('which is the one moment anybody actually knows it') add flavor at some cost to terseness.

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?

For an 11-parameter write tool with nested details and an output schema, the description covers the epoch mechanics, offset omission state, and evidence capture well. It does not address duplicate or repeated logging behavior, which matters given idempotentHint=false.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description still adds meaning: offset_value is defined as a signed clicks-to-add correction along the collar's direction, offset_source enumerates pull/counted/typed, and details is tied to the per-task details_fields published elsewhere.

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?

Opens with a specific verb and resource: 'Log a cleaning or maintenance job against a piece of equipment.' It also distinguishes itself from read-side siblings by pointing at list_grinders/list_machines for due state and from set_maintenance_offset by owning the offset recorded at log time.

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 conditions: record the offset only if you counted clicks at reassembly; any vocabulary task may be logged even if the maker advises against it; read due state from list_grinders/list_machines. No explicit when-not guidance relative to list_maintenance_due or set_maintenance_offset, which leaves some sibling ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ShotPulled toolsInspect
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