ShotPulled

Merge two coffees

merge_beans

Destructive

Fold one coffee into another when the same coffee was registered twice. Every bag, shot, recipe and recommendation of from_bean_id moves to into_bean_id; the active coffee follows if it was the one merged away; origins move only if the target has none. Where both hold a locked recipe for the same grinder, machine, program and drink, the newer lock wins and the older is deleted. The source coffee is archived, never deleted. Irreversible: confirm both numbers with the user first (list_beans shows them).

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": {
      "from_bean_id": "<from_bean_id>",
      "into_bean_id": "<into_bean_id>"
    },
    "name": "merge_beans"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Optional note, recorded on the surviving coffee's notes with the merge
`from_bean_id`	Yes	The duplicate: the coffee number that will be emptied and archived
`into_bean_id`	Yes	The coffee number that keeps everything

Output Schema

Name	Required	Description	Default
`moved`	Yes
`status`	Yes
`message`	Yes
`into_bean_id`	Yes
`active_followed`	Yes
`replaced_recipes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Far exceeds what the annotations convey: annotations only flag destructive=true and idempotent=false, while the description explains exactly what moves (bags, shots, recipes, recommendations), the conditional behaviors (origins only if target has none, newer lock wins and older is deleted), that the source is archived not deleted, and that the operation is irreversible.

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?

Leads with the trigger, then the consequences, then the safety warning — all within four sentences with no filler. The dense lock-conflict clause is the only heavy sentence, but it is information the agent cannot get elsewhere.

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

Completeness5/5

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

A destructive mutation with an output schema needs the description to cover data migration, edge cases and irreversibility; it does all three. Return values are covered by the output schema, so nothing material is missing.

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?

Schema coverage is 100% and the schema already labels from_bean_id as the duplicate to be archived and into_bean_id as the survivor, so the description is not the sole source. It still adds directional reinforcement and points the agent at list_beans to resolve the numbers before calling.

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 ('fold one coffee into another') plus the exact condition that motivates it ('when the same coffee was registered twice'). This clearly distinguishes merge_beans from update_bean and the register_* siblings.

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?

Gives an explicit trigger condition (duplicate registration) and a required pre-flight step: confirm both numbers with the user and look them up via list_beans. It does not name the non-duplicate alternative (update_bean) for cases where the coffees are genuinely distinct, so the when-not case is only implied.

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?