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.

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
`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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "grinder_id": {
+      "type": "integer"
+    },
+    "message": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "grinder_id",
+    "message"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJul 19, 2026

changedInput schema / properties / max_value / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedInput schema / properties / microns_per_step / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedInput schema / properties / min_value / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

First observedJun 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the write/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds genuine non-obvious behavior beyond that: registration does NOT force activation, and the reply's `active` field reveals which grinder is active. It does not cover auth requirements or side effects on existing grinders, so not a 5.

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?

Three tightly scoped sentences, each earning its place: what it creates, the conditional activation behavior, and the fallback action. Front-loaded with the core action.

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-value explanation is not needed, yet the description still points to the meaningful `active` field of the reply. Combined with annotations covering write safety, the description is complete for the call, though it is silent on required-permission context for a 14-param mutation.

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 description coverage is 79%, so the schema already documents most of the 14 parameters. The description only obliquely touches parameter meaning ('manual or electric' -> motor_type, 'dial settings scheme' -> setting_scheme) and adds no syntax or format detail beyond structured data. Baseline 3 is appropriate.

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') and clearly distinguishes itself from the sibling set_active by contrast. An agent can tell it apart from update_grinder/list_grinders without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the condition under which the new grinder becomes active (none active, or the active one archived) and names the alternative action (call set_active with its grinder_id) for the other case. This is prescriptive when-to-use guidance, not inference.

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?