Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Adjust_inventory

Update inventory by adjusting the current on-hand quantity with a specified amount, ensuring total stock stays below 100,000 units.

Instructions

API for updating inventory by adjusting the inventory amount from the current inventory on hand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesInventory ID
amountYesAmount must greater than or equal to 0 and less than 100,000 (0 <= amount + availableNumber < 100,000)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
availableNumberNoQuantity that is available and display on the storefront (Exclude ‘Reserved’ and ‘Ready to ship’ status)
onHandAmountNoQuantity in stock (Include ‘Reserved’ and ‘Ready to ship’ status)
readyToShipAmountNoQuantity that customers complete payment and wait to ship
reservedAmountNoQuantity that customers do not complete payment
Behavior2/5

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

No annotations provided. The description does not disclose side effects, authentication needs, or whether the operation is destructive. It only says 'updating', which is insufficient.

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 description is a single short sentence, which is concise. However, it is too vague to be fully effective.

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?

The description lacks context about return values, how the amount interacts with current inventory, and does not leverage the presence of an output schema to add clarity. Sibling tools are not compared.

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 adds no additional meaning beyond the schema, but does not contradict it either.

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

Purpose3/5

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

The description states it updates inventory by adjusting the amount, but it is ambiguous whether it sets absolute amount or adds a delta, especially given sibling tools Increase_inventory and Decrease_inventory.

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?

No guidance on when to use Adjust_inventory versus Increase_inventory or Decrease_inventory. The description does not mention any prerequisites or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/woraphol-j/lineshopping-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server