Skip to main content
Glama

Update Physical Product Inventory

update_physical_product_inventory

Update inventory quantities for a physical product managed by the authenticated Nas.com user. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "productId": "<productId>",
      "items": "<items>"
    },
    "name": "update_physical_product_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesItems to update in this request.
productIdYesProduct ID, from a Nas.com product listing for this business.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / items / description
      Added value: +"Items to update in this request."
    • addedInput schema / properties / productId / description
      Added value: +"Product ID, from a Nas.com product listing for this business."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, and the description adds meaningful context beyond that: entitlement gating, a grace-period state, and the rule never to proceed when access is blocked. What is still undisclosed is the mutation's effect semantics — whether a quantity change is applied as a delta or an absolute, and whether the update is atomic across the items array.

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?

Purpose is front-loaded in the first clause, then the gating rules follow in procedural order. Every sentence carries an actionable constraint — there is no restatement of the title or filler prose.

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 mutation tool the access-control story is thorough, and with a fully documented schema and annotations the definition is largely self-sufficient. The gap is effect semantics: an agent still cannot tell what happens to inventory levels beyond the request, nor what a partial or failed items array does to state.

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 and the description adds nothing further about parameters. Critically, it does not clarify the meaning of quantityChange (relative adjustment vs. absolute set), which is the single most consequential ambiguity in this schema and is not resolved by the schema itself.

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 opens with a specific verb+resource pair: 'Update inventory quantities for a physical product,' which clearly separates it from update_physical_product (product fields) and get_physical_product_inventory (read path). It stops short of naming those siblings explicitly, so the agent must infer the boundary from the resource noun alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use preconditions and hard exclusions: FREE businesses cannot use it regardless of feature rows, and check_business_tool_access must be called before collecting inputs. It also states the ordering of steps (name the gate tool, surface grace-period warning and resubscribe link, stop when blocked), which is exactly the kind of routing guidance that prevents wrong invocation.

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