ShotPulled

Set calibration offset

set_maintenance_offset

Idempotent

Record 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 what lets several of them compose for a recipe locked before all of them. Zero is a legitimate measurement and means "measured, and it had not moved" — omit offset_value entirely to clear it back to unmeasured.

Input Schema

TableJSON Schema

Name	Required	Description
`source`	No	How it was arrived at: pull, counted, or typed
`entry_id`	Yes	The maintenance entry that opened the epoch, from list_grinders
`evidence`	No	One line recording what it rested on, e.g. "Reference pull 1.38 g/s against 1.74 g/s locked."
`offset_value`	No	Clicks to ADD to a pre-clean reading to get the same grind today, signed along the collar's own number direction. 0 records "unchanged"; omit to clear the measurement

Output Schema

TableJSON Schema

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

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond the annotations by explaining the composition behavior of offsets, the semantics of zero as a legitimate measured value, and the effect of omitting offset_value to clear the measurement. These are non-obvious behavioral details that an agent could not infer from the annotations or the input schema alone.

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 dense but well-organized: the core action and object are front-loaded, the entry-vs-equipment distinction earns its place, and the zero/omission clarification prevents a classic edge-case mistake. No sentence is redundant or 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?

The description covers the essential call context, the composition semantics, and the value-clearing behavior, while the presence of an output schema covers return values. It assumes some familiarity with the concept of a calibration epoch, but both the description and the schema reference the same concept, giving the agent enough grounding for typical usage.

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?

With 100% schema description coverage, the baseline is 3. The description adds conceptual value by explaining why the offset is attached to the entry rather than equipment and by clarifying that zero must be treated as a real measurement. This supplements the offset_value schema description and helps the agent avoid common mistakes.

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 opens with a specific verb-resource pair ('Record how far a maintenance job moved the reference') and immediately constrains the target to 'an entry that opened a calibration epoch.' It also explicitly differentiates this tool from equipment-level operations by stating 'Takes an ENTRY, not a piece of equipment,' making the tool's purpose unambiguous.

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 clearly establishes when to use the tool: when recording an offset on the maintenance entry that opened a calibration epoch. It also gives an explicit exclusion—this is not for pieces of equipment—and explains why the entry-level attachment matters for composed offsets. However, it does not name alternative sibling tools or state conditions where another tool would be more appropriate.

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 sort cleanly into register_*, list_*, set_*, and log_* families with clear resource targets. The main ambiguity is between diagnose_shot and diagnose_preview, which are deliberately similar, and between get_dial_state and suggest_next_step, but the descriptions resolve these reasonably well.

Naming Consistency4/5

Naming is overwhelmingly consistent snake_case verb_noun, such as register_coffee, list_shots, update_shot, and set_active. Minor exceptions like kb_changelog next to get_kb_version and grinder_math break the pattern slightly.

Tool Count2/5

With 34 tools, the surface is well over the 25+ too-many threshold. The resource families are individually clear, but the assistant would be easier to navigate with fewer, more consolidated tools or less KB introspection surface.

Completeness3/5

The core dialing workflow is well covered: registration, shot logging, diagnosis, dial state, recipes, and maintenance. However, most registered entities such as grinders, machines, waters, scales, and programs have create+list but no update/delete, and recipes have no unlock/delete lifecycle.

Resources

Need Help?