ShotPulled

Register a water recipe

register_water

Input Schema

TableJSON Schema

Name	Required	Description
`gh`	No	General hardness (GH) in ppm
`kh`	No	Karbonate hardness (KH) in ppm
`tds`	No	TDS in ppm
`name`	Yes	Water formulation name, e.g. Lotus Light & Bright, Third Wave Water
`type`	No	Type, e.g., mineralized, tap, distilled, RO
`notes`	No	Additional notes
`sodium`	No	Sodium concentration in ppm
`calcium`	No	Calcium concentration in ppm
`magnesium`	No	Magnesium concentration in ppm

Output Schema

TableJSON Schema

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

Schema Changelog

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

First observedSep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already signal that this is not a read-only operation, but the description adds no behavioral detail beyond that, such as whether duplicate names overwrite, whether registration requires approval, or any side effects. It does not contradict the annotations.

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 sentence with no filler, front-loading the core action and resource. It is appropriately sized for the simplicity of the tool.

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?

For a registration tool, the description combined with full schema coverage, annotations, and an output schema provides enough context for an agent to select and invoke the tool. It is slightly incomplete only because it omits usage guidance relative to sibling tools, but that is covered under usage_guidelines.

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?

The input schema has 100% property description coverage, so the schema carries the parameter documentation burden. The description adds no additional parameter meaning beyond what is already in the schema.

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 the specific verb 'Register' with the resource 'water formulation', which matches the title and clearly identifies the tool's purpose. It also distinguishes this tool from sibling register_* tools by naming water as the entity, and custom/commercial scope adds useful clarity.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool over alternatives such as list_waters or update_* tools. No exclusions, prerequisites, or comparison with sibling tools are provided; usage context is only implied by the name and title.

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?