ShotPulled

Register a grinder

register_grinder

Register 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 with its grinder_id to switch to it. The active field of the reply says which.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "motor_type": "<motor_type>",
      "burr_type": "<burr_type>",
      "setting_scheme": "<setting_scheme>",
      "direction_convention": "<direction_convention>",
      "nominal_step": "<nominal_step>"
    },
    "name": "register_grinder"
  }
}

Input 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
`catalog_id`	No	Optional: the maintenance catalog model this is (the `id` of a catalog row, e.g. rancilio-silvia), when it was registered from the catalog. Its maintenance then comes from that model's researched record. "none" says it is not in the catalog.
`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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / catalog_id / description

Previous value: -"Optional — the maintenance catalog model this is (the `id` of a catalog row, e.g. rancilio-silvia), when it was registered from the catalog. Its maintenance then comes from that model's researched record. \"none\" says it is not in the catalog."New value: +"Optional: the maintenance catalog model this is (the `id` of a catalog row, e.g. rancilio-silvia), when it was registered from the catalog. Its maintenance then comes from that model's researched record. \"none\" says it is not in the catalog."

Changed2 schema fields changedSep 27, 2026

addedOutput schema / properties / active
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "status",
-  "grinder_id",
-  "message"
-]New value: +[
+  "status",
+  "grinder_id",
+  "active",
+  "message"
+]

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / catalog_id

Added value: +{
+  "description": "Optional — the maintenance catalog model this is (the `id` of a catalog row, e.g. rancilio-silvia), when it was registered from the catalog. Its maintenance then comes from that model's researched record. \"none\" says it is not in the catalog.",
+  "type": "string"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare non-readOnly, non-idempotent, non-destructive, but the description adds the crucial side effect the annotations cannot express: activation is conditional on no active/archived grinder, and the reply's `active` field tells which. That is genuine behavioral disclosure beyond structured data.

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?

Three tight sentences with the core action front-loaded and the conditional-activation rule immediately after. No filler, though the final sentence about the `active` field is slightly compressed in wording.

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?

An output schema exists so return values need not be detailed, yet the description still points to the `active` reply field, which is the one output an agent must act on. Combined with the activation rule, an agent has enough to call it correctly; only the post-creation edit path is offloaded to inference.

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

Parameters3/5

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

Schema coverage is 79%, so the schema already documents nearly all 14 parameters including the setting_scheme and catalog_id semantics. The description adds only the aggregate concept of a 'dial settings scheme' and does not clarify any individual parameter beyond what the schema provides.

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?

States a specific verb and resource ('Register a manual or electric grinder with its dial settings scheme'), which immediately separates it from update_grinder and set_active in the sibling list. The scope (creating a new grinder record vs. mutating state) is 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?

Explicitly names the alternative for switching: 'otherwise call set_active with its grinder_id to switch to it,' and the condition under which this tool activates the grinder. It does not mention update_grinder for later edits, so it stops one step short of full routing guidance.

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?