Skip to main content
Glama

Create stock issue

well_create_stock_issue

Record a stock issue for a product at a location of the current workspace: stock left (shipped or sold). The stock level of the product at that location follows in the same step.

Use this tool when the user says stock left, was shipped or was sold. Find the product_id first with well_list_products or well_get_product. A location_id is the id of a location of the workspace.

REQUIRED: product_id, location_id, quantity (a positive decimal string). OPTIONAL: occurred_at (ISO 8601 with an offset; the current time when absent). Send the same occurred_at when retrying: the same movement sent twice is recognised and adds nothing.

A level below zero is stored and flagged, never refused. When a connected tool owns the stock of the location, the call fails: tell the user to change the stock in that tool. A workspace routine approved for this tool runs it unattended and writes stock with no one watching.

Returns { success: true, movement, replayed, location_id, location_quantity, negative_level, stock_quantity } on success, or { success: false, error } on failure.

Input Schema

NameRequiredDescriptionDefault
quantityYesA positive decimal, at most 4 decimals, as a string.
product_idYesThe product the stock moves for, from well_list_products or well_get_product.
location_idYesThe workspace location the stock moves at.
occurred_atNoWhen it happened, an ISO 8601 date and time with an offset. The server clock when absent. Send the same value when retrying, so a retry is recognised and adds nothing.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
codeNo
errorNo
successYes
movementNo
replayedNo
location_idNo
reply_linesNo
negative_levelNo
stock_quantityNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
location_quantityNo
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / occurred_at / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / movement / properties / from_location_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / movement / properties / from_location_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / movement / properties / to_location_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / movement / properties / to_location_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / near_candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "company_id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "company_id",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / near_candidates_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / reply_lines
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses real behavior: negative levels are stored and flagged rather than refused, the call fails when a connected tool owns the location's stock (with remediation advice to the user), an approved workspace routine can run it unattended, and retries with the same occurred_at are deduplicated. Those are exactly the operational facts an agent cannot get from readOnlyHint/destructiveHint=false.

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?

The trigger and the scope constraint are front-loaded, and the REQUIRED/OPTIONAL block is easy to scan. The closing sentence enumerating the return fields duplicates the existing output schema and is the only clearly wasted line.

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?

For an 8-parameter write with no nested objects, the description covers the trigger, prerequisites, defaults, retry idempotency, negative-stock policy and the connected-tool failure path, while the output schema and annotations carry the return shape and safety profile.

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 baseline is 3. The description restates the required trio and the occurred_at default/retry rule, which the schema already documents, and adds no new semantics for workspace_id, conversation_id, idempotency_key or workspace_scope.

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 gives a specific verb and resource ("Record a stock issue for a product at a location") plus the business framing "stock left (shipped or sold)", and notes that the location's stock level updates in the same step. It does not explicitly name the closely related siblings well_create_stock_receipt / well_create_stock_adjustment / well_create_stock_correction, so an agent must infer the boundary from the framing alone.

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?

"Use this tool when the user says stock left, was shipped or was sold" gives a concrete trigger phrase, and it routes the agent to well_list_products / well_get_product to obtain the product_id first. It still lacks an explicit negative case (e.g. incoming stock belongs to create_stock_receipt), which is the main gap for such a crowded stock-tool family.

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