clover-mcp

create_modifier_group

Create a new modifier group for a Clover merchant's inventory, e.g., 'Milk options'. Blocks duplicate names, previews with dry-run, and confirms before writing.

Instructions

Modifies merchant data. Create a new modifier group (e.g. "Milk options").

Duplicate guard: refuses if a group with the same name (case-insensitive) already exists. Previews on dry_run; confirms via MCP elicitation or confirm=True before writing. Requires INVENTORY_W.

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>"
    },
    "name": "create_modifier_group"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`confirm`	No
`dry_run`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Aug 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing duplicate guard (case-insensitive name check), dry-run preview via dry_run, confirmation via MCP elicitation or confirm=True, and the required INVENTORY_W permission. These are non-obvious behavioral details that inform agent decisions.

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?

Four tight sentences: one intro/purpose, one example, two covering guards and permissions. No fluff, all information is operationally valuable and easy to scan.

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?

Given the output schema exists, return values need not be explained. The description covers the key operational aspects: preconditions (permission), safety (dry-run, confirmation), and failure mode (duplicate guard). This is sufficient for an agent to use the tool correctly.

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 0%, so description must compensate. It explicitly explains dry_run and confirm behavior, and uses 'Milk options' as an example for name. This adds meaning beyond the bare schema, though name's format isn't fully detailed.

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?

Clearly states the tool's action: 'Create a new modifier group' with an example ('Milk options'). Distinguishes from sibling create_modifier by explicitly using 'group', making the resource type 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?

Provides clear context: creating a modifier group, not a modifier. However, it doesn't explicitly mention when not to use this tool or name alternatives like create_modifier. The example and naming imply the boundary, so it's clear but lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server