Skip to main content
Glama

Product GTIN-13 metadata

bpj_product_gtin_metadata
Read-onlyIdempotent

Verify a GTIN-13 check digit and build Product metadata with brand and SKU.

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": {
      "name": "<name>",
      "brand": "<brand>",
      "sku": "<sku>",
      "gtin": "<gtin>"
    },
    "name": "bpj_product_gtin_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYes
gtinYes
nameYes
brandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds that it verifies a GTIN-13 check digit and constructs metadata, but it does not explain invalid check-digit behavior or the shape of the returned metadata.

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 front-loaded sentence with no wasted words. The phrasing 'build Product metadata with brand and SKU' is slightly fragmentary, but the structure is clear and appropriately concise.

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?

For a tool with four required string parameters and no output schema, the description should say more about expected inputs and return behavior. It omits the 'name' parameter and does not describe what happens on validation failure or what metadata object is returned.

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 of explaining the four required parameters. It mentions GTIN-13, brand, and SKU, but omits the required 'name' parameter and provides no format or validation details beyond the check-digit hint.

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?

The description states specific actions: verify a GTIN-13 check digit and build Product metadata. It clearly identifies the resource and the fields involved, though it does not explicitly differentiate this tool from siblings such as bpj_gtin_normalize.

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 explicit guidance on when to use this tool versus alternatives, nor any stated exclusions or prerequisites. The task is implied by the verb 'Verify' and 'build', but the description does not help an agent choose between this and related GTIN tools.

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.