Skip to main content
Glama

repairinfo: repairability of devices

Look up a barcode

lookup_barcode
Read-onlyIdempotent

Find a device by its EAN/GTIN barcode (8 to 14 digits), as printed on the box or shelf label. Returns the same data as get_device.

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": {
      "ean": "<ean>"
    },
    "name": "lookup_barcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
eanYesEAN-8, UPC-A, EAN-13 or GTIN-14

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely useful non-annotation context: the digit-length constraint on input and the fact that the payload is identical to get_device, which substitutes for the absent output schema. It does not say what happens on a not-found barcode, which is the main remaining gap.

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, no filler, front-loaded with the lookup action and input format, with the output-equivalence note placed second where it belongs.

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 single-parameter read-only lookup with rich annotations and a declared output equivalent, nothing essential is missing. Only the not-found/failure behavior is left unspecified, a minor omission for a tool of this simplicity.

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 100% and already names the accepted symbologies, so the schema does most of the work. The description still adds value by restating the 8–14 digit constraint and grounding the parameter in the real-world artifact ('as printed on the box or shelf label'), clarifying that a scanned barcode string is expected.

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?

The description pairs a specific verb with a specific resource ('Find a device by its EAN/GTIN barcode'), states the accepted input format (8 to 14 digits), and explicitly ties the result to get_device, so an agent can distinguish this lookup route from an ID-based route without opening the schema.

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

Usage Guidelines4/5

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

Usage context is clear: call this when the identifier in hand is a printed barcode from a box or shelf label rather than a device ID. It references get_device as the equivalent-output path but does not explicitly state when NOT to use this tool or that get_device takes an ID instead, so there is no full exclusion statement.

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