ShotPulled

Register a grinder

register_grinder

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The name/model of the grinder, e.g. Kinu M47
`notes`	No	Additional notes
`photo`	No	Photo path or URL
`archived`	No	1 if archived, 0 if active
`burr_type`	Yes
`max_value`	No	Optional travel max bounds
`min_value`	No	Optional travel min bounds
`motor_type`	Yes
`nominal_step`	Yes	Smallest adjustment increment (e.g. 1 click or 0.1collar units)
`setting_scheme`	Yes	Collar mark style: single clicks or compound (rotation.number.clicks)
`components_spec`	No	JSON mapping string representing compound adjustment math
`microns_per_step`	No	Optional mechanical burr travel microns per nominal step
`direction_convention`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`grinder_id`	Yes

Schema Changelog

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

First observedSep 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations are all false and provide no real safety or behavior context, so the description carries the disclosure burden. It only says 'Register,' without explaining persistence effects, uniqueness expectations, validation requirements, or any other runtime behavior.

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 a single front-loaded sentence with no filler. It conveys the core action, the accepted grinder types, and the key settings aspect in minimal words.

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

Completeness2/5

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

For a 13-parameter registration tool with an output schema, the description is quite thin. It does not explain registration prerequisites, the relationship to grinder_math or set_grinder_position, or when compound settings/components_spec become relevant.

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

Parameters2/5

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

Schema coverage is 77%, and the description adds only the terms 'manual or electric' and 'dial settings scheme,' which loosely map to motor_type and setting_scheme. It does not add meaning for required but undocumented parameters like burr_type or direction_convention.

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 uses a specific verb ('Register') and resource ('grinder'), and adds a meaningful qualifier: 'manual or electric ... dial settings scheme.' This clearly distinguishes it from sibling tools like list_grinders and set_grinder_position.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its use when adding a new grinder to the system, but it does not explicitly state when to use it versus alternatives such as list_grinders, set_grinder_position, or grinder_math. No exclusions or selection criteria are provided.

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?