Simple Inventory Management

find_item_by_barcode

Find an inventory item by its barcode (UPC, EAN, or Code 128 / SKU value) within the user's company. Returns the matching item or an error if none matches.

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": {
      "barcode": "<barcode>"
    },
    "name": "find_item_by_barcode"
  }
}

Input Schema

Name	Required	Description	Default
`barcode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does valuable work by disclosing the outcome contract ('returns the matching item or an error if none matches'), but it omits whether matching is exact versus fuzzy, what permissions are required, or whether multiple matches are possible.

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?

Two sentences, zero waste, with the core action front-loaded and the return/error behavior trailing it. Nothing is repeated from the schema.

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

Completeness4/5

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

For a one-parameter lookup with no annotations and no output schema, the description covers action, input domain, scope, and failure mode. Only the exact-match semantics and the shape of the returned item remain unstated.

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

Parameters4/5

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

Schema coverage is 0% and the single parameter is an undescribed string, so the description must compensate. It does so by defining the accepted barcode families (UPC, EAN, Code 128 / SKU value), which materially clarifies what value to supply.

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?

States a specific verb and resource ('Find an inventory item by its barcode') and enumerates accepted barcode formats (UPC, EAN, Code 128 / SKU). It implicitly distinguishes itself from the sibling list/get tools by being a barcode-keyed lookup, but it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Adds useful scoping with 'within the user's company', which tells the agent the search domain. However, it gives no explicit when-to-use versus siblings such as get_inventory, list_inventory_units, or find_units_by_custom_field, and no when-not-to-use conditions.

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

All Simple Inventory Management tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?