ShotPulled

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 — so record the offset here if you counted the clicks while reassembling, which is the one moment anybody actually knows it. Read the available tasks, their intervals and their due state from list_grinders.

Input Schema

TableJSON Schema

Name	Required	Description
`note`	No	Optional — what you did, and anything that surprised you
`task`	Yes	Which maintenance job was performed
`details`	No	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
`evidence`	No	One line recording what the measurement rested on, e.g. "Counted 6 clicks coarser at reassembly."
`equipment_id`	Yes	The ID of that piece of equipment
`offset_value`	No	The 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_at`	No	When it was done (ISO 8601 or YYYY-MM-DD HH:MM:SS, UTC). Defaults to now; backdating is fine
`disturbs_zero`	No	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
`offset_source`	No	How the offset was arrived at: pull (a reference shot), counted (clicks counted at reassembly), typed (asserted directly)
`equipment_kind`	Yes	Which kind of equipment this job was done on

Output Schema

TableJSON Schema

Name	Required	Description	Default
`entry`	Yes
`message`	Yes
`entry_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 16, 2026

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"
+]

AddedAug 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds important behavioral context beyond the sparse annotations, especially the calibration-epoch effect of disassembly and the significance of recording offsets at reassembly. It does not cover every side effect, but it explains the most subtle and consequential behavior of the tool.

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?

The description is compact and front-loaded, with the core purpose in the first sentence and the most important caveat immediately following. Every clause earns its place, and it avoids repeating what the schema already documents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 parameters and a nested object, the description plus the fully covered schema provide a complete picture. It explains the key domain behavior, points to the correct catalog source, and the output schema removes the need to document return values.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description meaningfully enriches the offset_value and task parameters by explaining their role in the calibration epoch and pointing to list_grinders for the task catalog. Other parameters are already well described in the schema.

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?

The description clearly states the tool's action and resource: logging a cleaning or maintenance job against a piece of equipment. It conveys the domain-specific calibration-epoch concept, which helps distinguish it from other logging tools like log_shot, though it does not explicitly contrast itself with those siblings.

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 gives concrete guidance on when to record an offset and directs the agent to list_grinders for available tasks, intervals, and due states. It does not explicitly state when not to use this tool or name alternatives such as set_maintenance_offset, but the usage context is clear.

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?