Skip to main content
Glama

adjust_store_stock

DestructiveIdempotent

Record a stock increase or decrease for a product in the approved store. Reuse the same adjustment ID and details on retry.

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": {
      "id": "<id>",
      "productId": "<productId>",
      "quantity": "<quantity>",
      "reason": "<reason>"
    },
    "name": "adjust_store_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
reasonYes
quantityYes
productIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value by operationalizing idempotency ('Reuse the same adjustment ID and details on retry'), which tells the agent exactly how to avoid duplicate stock movements. It still omits what makes the call destructive in practice, e.g. whether a decrease below available stock fails, and whether adjustments are logged or reversible.

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?

Two short sentences with no filler; the core action is front-loaded and the retry/idempotency instruction follows immediately. Every clause contributes information an agent needs.

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

Completeness3/5

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

For a destructive, non-read-only mutation with no output schema and 0% schema documentation, the definition is only minimally sufficient: it never states what a successful call returns or whether errors (insufficient stock, unknown product, duplicate id) surface as failures. Annotations carry the safety burden, which keeps this from being lower.

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 description coverage is 0% across four required parameters, so the description carries the burden and only partly meets it: it conveys that 'id' is the idempotency key and that 'quantity' is a signed delta (increase or decrease). It says nothing about the 'reason' field (free text, max 500 chars) or that productId must reference an existing catalogue item.

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?

The description states a specific verb and resource ('Record a stock increase or decrease for a product') plus a scope constraint ('in the approved store'), which is enough to distinguish it from catalogue readers like list_store_catalogue and from save_store_product. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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?

There is no when-to-use guidance relative to alternatives: nothing says when to adjust stock versus writing the product record via save_store_product, nor whether the store must already be approved/enabled before calling. The retry sentence is about call mechanics, not tool selection, so it does not fill this gap.

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.

Resources