MCP Inflow Ingredients

create_stock_adjustment

Modify inventory quantities for products by creating stock adjustments with specified locations, products, quantities, and adjustment reasons.

Instructions

Create a stock adjustment to modify inventory quantities for one or more products

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": {
      "stockAdjustmentId": "<stockAdjustmentId>",
      "locationId": "<locationId>",
      "lines": "<lines>"
    },
    "name": "create_stock_adjustment"
  }
}

Input Schema

Name	Required	Description
`adjustmentDate`	No	Date of adjustment (ISO format)
`adjustmentReasonId`	No	Reason ID for the adjustment
`lines`	Yes	Array of products and quantities to adjust
`locationId`	Yes	Location ID where adjustment occurs
`notes`	No	Notes about the adjustment
`stockAdjustmentId`	Yes	UUID for the adjustment (generate with crypto.randomUUID())

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'modifies inventory quantities,' implying a write operation, but lacks details on permissions required, whether changes are reversible, rate limits, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence that front-loads the key action and resource. There's no redundancy or unnecessary detail, making it easy to parse quickly.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., confirmation, error details), behavioral constraints, or how it fits with sibling tools, leaving significant gaps for an agent to use it effectively.

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 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond implying adjustments can be for 'one or more products' (hinting at the 'lines' array), but doesn't clarify parameter interactions or usage nuances. This meets the baseline for high schema coverage.

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 clearly states the action ('create a stock adjustment') and the resource ('inventory quantities for one or more products'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'list_stock_adjustments' or 'get_stock_adjustment', which would require mentioning it's for creating new adjustments rather than retrieving existing ones.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing valid product IDs or location IDs), nor does it compare to sibling tools like 'update_ingredient' for inventory changes, leaving the agent without context for tool selection.

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

Deploy Server