Skip to main content
Glama

ShearQuery — Barber & Beauty Industry Data

Change your supply cart

update_supply_cart

Change the signed-in member's supply cart (the same cart as the website's product pages). action "add" adds qty of a product (product_id from shop_supplies; option is the option's label for a product with options), on top of any already there. "set" sets a product's quantity (0 removes it). "remove" takes a product out. "clear" empties the cart. Nothing is bought or charged. Say what changed and the cart's new total from the result.

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": {
      "action": "<action>"
    },
    "name": "update_supply_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNoFor add (default 1) or set.
actionYes
optionNoThe option's label, e.g. '#1005'.
product_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

With annotations present, the description adds real value: it discloses additive semantics for 'add' (not a replacement), that qty 0 removes the item, that clearing empties the cart, and crucially that 'Nothing is bought or charged', which reconciles the mutating write with destructiveHint=false. It does not add anything about authorization (beyond 'signed-in member'), failure modes, or confirmability of the change, so it does not fully clear the lower bar annotations set.

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?

Front-loaded with the resource and the website-cart equivalence, then the action modes, then the no-charge caveat and the reporting instruction — a sensible order with no wasted sentences. The parenthetical nesting ('product_id from shop_supplies; option is the option's label for a product with options') makes one sentence dense enough to require re-reading.

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?

No output schema exists, and the description closes that gap by instructing the agent to report what changed and the cart's new total from the result. Combined with the explicit no-purchase caveat and per-action semantics, an agent has everything needed to invoke this correctly and report back.

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

Parameters5/5

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

Schema coverage is only 50% (product_id has no schema description), and the description compensates fully: product_id is sourced from shop_supplies, option is defined as the option's label for a product with options, qty is scoped to add (default 1) and set, and the action enum is individually explained. Every one of the four parameters gains meaning beyond the schema text.

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 ('Change the signed-in member's supply cart') and immediately disambiguates it from lookalikes by identifying the cart as 'the same cart as the website's product pages' and by sourcing product_id from shop_supplies. An agent can distinguish this mutation tool from my_supply_cart (read) and shop_supplies (catalog) without opening a schema.

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?

Each of the four enum values is given a concrete operating rule ('add' is additive on top of existing quantity, 'set' with 0 removes, 'remove' takes out, 'clear' empties), which tells the agent exactly which mode to pick for a given intent. It also names shop_supplies as the source of product_id. It stops short of explicitly stating when not to use this tool versus siblings such as discard_change or undo_change.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.