resolve_gtinResolve a GTIN to its procurement readiness signal. Zero-pads input to 14 digits.
| Name | Required | Description | Default |
|---|---|---|---|
| gtin | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the zero-padding behavior, which is useful, but does not state whether the operation is read-only, how invalid GTINs are handled, or what happens for inputs that cannot be resolved.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, with two short sentences that front-load the core purpose and then add the key normalization detail. Every sentence earns its place with no redundant wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with an output schema, the description covers the essential invocation detail: the GTIN input and the normalization rule. Since an output schema exists, the return shape does not need to be described, though a note on when to use it would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% parameter coverage, so the description must compensate. It adds meaningful semantic detail by explaining that the input is zero-padded to 14 digits, but it does not clarify accepted formats, length limits, or validation behavior for the gtin parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Resolve a GTIN') and a distinct outcome ('procurement readiness signal'), which clearly differentiates it from sibling resolve tools. 'Procurement readiness signal' is not fully defined, but the resource and purpose are unambiguous enough.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus the many sibling tools such as resolve_node, resolve_scope, or resolve_sparks. The only usage-related detail is the zero-padding normalization behavior, but no selection criteria or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools overlap heavily: resolve_gtin, resolve_sparks, and get_signal_chain all resolve GTINs to different but closely related signals, and resolve_node vs node_market both return the same node with makers/retailers counts. Agents will struggle to pick the correct tool without reading deep into descriptions.
Most tools follow a clear verb_noun pattern (check_, count_, find_, get_, list_, resolve_), but node_market breaks the pattern and the get_ vs resolve_ distinction is not obvious. Overall readable with only minor deviations.
14 tools is well-scoped for a CPG knowledge graph covering GTIN resolution, eligibility, supply/demand search, node metadata, taxonomy, and brand coverage. Each tool reasonably earns its place without overwhelming the surface.
The surface covers the apparent domain comprehensively: GTIN resolution, eligibility checks, maker/retailer discovery, node/spine queries, SKU taxonomy, brand listings, signal chains, and registries. For a read-only knowledge graph, there are no obvious dead ends or missing core operations.