Skip to main content
Glama

Confirm a beverage alcohol GTIN

confirm_gtin
Read-onlyIdempotent

Confirm one GTIN as a beverage alcohol product the trade will move: well-formed, seen (pages and dates), CUVEE category, strength, container, deposit, excise class, age-gated, markets and banners seen, signed. Unknown means no observation, never a guess.

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": {
      "gtin": "<gtin>"
    },
    "name": "confirm_gtin"
  }
}

Input Schema

NameRequiredDescriptionDefault
payNoOptional. true asks for the paid confirm: an x402 settlement on Base (HTTP 402 with the offer until PAYMENT-SIGNATURE is sent) and a signed receipt with the answer. Without it the confirm is open access.
gtinYesThe GTIN as printed: 8, 12, 13 or 14 digits (spaces allowed)
marketNoOptional ISO 3166-1 alpha-2 market (uk, de, fr …) to say whether the product was seen there

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety and repeatability are covered. The description adds genuinely useful semantics not in the annotations: "Unknown means no observation, never a guess" establishes that a null result is an evidence gap rather than a negative determination. It does not mention the open-access/paid split or signing behavior, which lives only in the schema.

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 verb-and-resource lead is front-loaded, and the single trailing sentence about unknown results is high-value rather than filler. The long attribute list is dense and jargon-heavy ("CUVEE category", "excise class"), which costs a point on readability but not on correctness.

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?

With no output schema, the description carries the burden of describing the answer, and it does so by enumerating every confirmed attribute, so an agent can predict the response shape. The remaining gap is that the paid/open-access distinction and receipt behavior appear only in the input schema, not in the description.

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

Parameters3/5

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

Schema coverage is 100%, including the optional paid-confirm flag and the ISO market selector, so the baseline is 3. The description corroborates meaning by listing "markets and banners seen" and "signed" as outputs, implicitly tying the market and pay inputs to what comes back, but it adds no format or constraint detail beyond the schema.

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?

"Confirm one GTIN as a beverage alcohol product" names a specific verb (confirm), a bounded resource (one GTIN), and the domain, then enumerates exactly what is being confirmed: well-formedness, observation evidence, CUVEE category, strength, container, deposit, excise class, age-gating, markets/banners, and signing. An agent knows precisely what question this tool answers 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?

"Confirm one GTIN" plus the qualifier "the trade will move" makes the intended context clear: vetting a single product for commercial movement. "Unknown means no observation, never a guess" guides interpretation of the answer. There is no explicit when-not guidance or named alternative, but no siblings exist to route against, so the gap is minor.

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