Skip to main content
Glama
mcp-erp-server

mcp-erp-server

by aldemarluz

Stock levels

inventory_stock
Read-only

Retrieve on-hand, reserved, and available stock quantities by product SKU and location to check inventory availability.

Instructions

On-hand, reserved and available quantity per product and location.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inventory_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNo
locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes that this is a safe, non-mutating read. The description does add value by naming the three quantity types the response will carry, which partially substitutes for the absent output schema, but it says nothing about aggregation behavior, pagination, or whether missing products yield zero or are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence fragment is efficient with no wasted words, but it is so terse that it reads as a column header rather than a tool definition. Conciseness is achieved at the cost of specification.

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 low-complexity, two-optional-parameter read tool with no output schema, naming the returned quantity fields is useful and largely sufficient. The gap is the missing explanation of default scope when both filter parameters are absent, which an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it only loosely maps 'per product and location' to the sku and location parameters. It never clarifies that both parameters are optional, nor whether omitting them returns the full catalog of stock levels, which is the key semantic question for an agent with zero required parameters.

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 fragment names a specific resource (stock levels) and the quantities returned (on-hand, reserved, available) broken down per product and location, but it has no verb, so an agent must infer whether this retrieves, lists, or computes. It does not distinguish itself from siblings like sales_get_price or finance_receivables.

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, no mention of when stock data is preferable to price or order tools, and no statement about what happens when sku or location is omitted. The agent is left to infer usage entirely from the name and the sibling list.

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