Skip to main content
Glama

resolve_digital_link

Read-onlyIdempotent

Use this tool to get the published EU Digital Product Passport (DPP) behind a GS1 Digital Link QR or a GTIN (optionally with lot/serial). Returns the versioned, immutable passport JSON (Core vocabulary), its version and hash when Cycle hosts it; otherwise says who hosts the link and how to request it. Read-only, no account needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_digital_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotNoOptional lot.
gtinNoGTIN if you have no link.
serialNoOptional serial.
digital_linkNoGS1 Digital Link URL from a QR code, e.g. https://id.cycle-platform.com/01/09506000134352/21/U1

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: it returns a versioned, immutable Core-vocabulary passport with its version and hash when Cycle hosts it, and otherwise reports who hosts the link and how to request it. That non-Cycle-hosted fallback path is exactly the kind of behavior annotations cannot convey.

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?

Three sentences, front-loaded with the verb and resource, then inputs, then return/fallback behavior, ending with the access precondition. Every clause carries information; nothing is redundant with the schema or annotations.

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 an output schema present and full parameter coverage, the description need not spell out the response shape, and it still characterizes the two outcome branches. Remaining gaps are minor: no mention of error behavior for unresolvable or malformed links, and no note on the relationship to sibling validation tools.

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%, so per-parameter documentation is already handled and baseline would be 3. The description still adds relationship semantics the schema does not: the link OR the GTIN (optionally with lot/serial) are alternative identification paths rather than co-required inputs, which is meaningful when zero parameters are required.

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?

States a specific verb ('get') and a specific resource ('the published EU Digital Product Passport'), plus the two input routes (GS1 Digital Link QR or GTIN with optional lot/serial). An agent can tell this retrieves a passport rather than building a link or creating a DPP. It stops short of naming a sibling such as build_gs1_digital_link to sharpen the boundary, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

'Use this tool to get...' plus 'Read-only, no account needed' gives an implied usage context, and the fallback sentence tells the agent what happens when Cycle does not host the passport. However, there is no explicit when-not guidance and no named alternative for cases like building or validating a digital link, leaving the routing decision 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