Skip to main content
Glama
Sign In

1lev1

by io.github.Avi-ADAM
OverviewDiscussionsAdmin

setShopStockTool

Update the shelf stock of a product or of one of its variants. Operational change (§4.6): any rikma member may do it, it applies at once, and prices are never touched. Two modes: set counts the shelf ("there are 7"), add adds a delivery ("12 came in"), reading the quantity on the server first so a sale that landed meanwhile is not overwritten. Use quant=-1 for unlimited. A product that is sold by variant keeps its stock on the variants (Matanot.quant is not used). Members only. Docs: https://1lev1.com/mcp#setShopStockTool

Input Schema

NameRequiredDescriptionDefault
modeNo`set` counts, `add` delivers. Default set.
valueNoUnits: the new count (`set`) or how many came in (`add`). Ignored when unlimited=true.
productIdYesMatanot id (from listRikmaProducts).
projectIdYesRikma id.
unlimitedNoPass true for unlimited stock (-1).
variantIdNoVariant id (from listRikmaProductVariants or listRikmaProducts). Required when the product has variants. Pass null/omit for a simple product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / variantId / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / variantId / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: applies immediately, never touches prices, only members may invoke, and the add path reads server-side quantity first to avoid clobbering concurrent sales — which is consistent with idempotentHint=false. However, the stale 'quant=-1' reference conflicts with the actual 'unlimited' parameter and could mislead an agent.

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-loads the action and mode distinction, then adds preconditions and the variant caveat in a compact paragraph; the docs link is unobtrusive. The stray 'quant' reference is the only wasted/confusing content.

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?

With 6 parameters, full schema descriptions, and no output schema, the description covers permissions, side effects, concurrency behavior, and variant handling adequately. Return/confirmation behavior is not described, but that is a minor gap given the rich schema and annotations.

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 coverage is 100%, so baseline is 3; the description's mode explanation and variant rule largely restate schema text. The 'sale that landed meanwhile' nuance is useful, but the 'quant=-1' mention references a parameter name that does not exist in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update the shelf stock of a product or of one of its variants') and narrows scope to stock only, which separates it from the general updateRikmaProductTool. It never names that sibling explicitly, so the differentiation is implied rather than stated.

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?

Explicitly explains the two modes (set counts existing units, add records a delivery) with concrete examples, states the members-only precondition, and specifies the variant rule. It does not point to an alternative tool or say when not to use it, e.g. for catalog/price edits.

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

All 1lev1 toolsInspect
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