Skip to main content
Glama

Match count barcode

match_count_barcode
Destructive

Tell a count which item a scanned barcode is. Use it for a barcode that compare_count could not match, or matched to several items. Send count_id, the barcode as it appears on the line, and item_id. item_id null removes the hand match. Either way, run compare_count again afterwards. An applied count is read-only. Requires the stock plan feature.

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": {
      "count_id": "<count_id>",
      "barcode": "<barcode>",
      "item_id": "<item_id>"
    },
    "name": "match_count_barcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
barcodeYes
item_idYes
count_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

The annotations declare destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: the item_id null path removes an existing hand match, an applied count is read-only, and the stock plan feature is a prerequisite. It still does not say what happens when the barcode is unknown or what the call returns, so it stops short of full behavioral disclosure for a destructive mutation.

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?

Five short sentences, each doing distinct work: purpose, trigger, argument payload, null behavior, follow-up, precondition. The alternative and the follow-up requirement are stated where an agent will read them, with no restatement of the tool name or filler.

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 three-parameter destructive mutation with no output schema, the definition covers trigger, arguments, edge-case semantics, follow-up, read-only guard, and entitlement prerequisite. The only gap is the failure mode for a barcode that matches nothing and whether the call returns anything the agent should inspect.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: count_id identifies the count, barcode must be "as it appears on the line" (a non-obvious formatting requirement), and item_id's null value has a distinct removal semantic. That is meaningful semantics the JSON schema alone cannot convey.

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

Purpose5/5

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

"Tell a count which item a scanned barcode is" is a specific verb and resource, and the description immediately positions it against compare_count, which handles the normal matching path. An agent can distinguish this hand-match override from the general comparison sibling without opening either schema.

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 an explicit trigger (only when compare_count could not match, or matched several items) and a mandatory follow-up ("run compare_count again afterwards"), plus the inverse operation via item_id null. Nothing about when to reach for this tool versus compare_count is left to inference.

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