Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_verify_dpp

Read-onlyIdempotent

Resolve an EU ESPR Digital Product Passport using a GS1 Digital Link (GTIN + serial) or passport UID, without an API key.

Instructions

Publicly resolve an EU ESPR Digital Product Passport via GS1 Digital Link (gtin + serial) or passport uid without requiring an API key.

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": "climeq_verify_dpp"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoDirect Digital Product Passport UID if resolving by UID.
gtinNoGS1 GTIN-14 / EAN code (use together with `serial`).
serialNoItem serial number (use together with `gtin`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description's one real addition is 'without requiring an API key', which usefully signals public/unauthenticated access. It says nothing about failure behavior for invalid or unresolvable identifiers, so it is a modest rather than rich contribution.

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?

A single front-loaded sentence with the verb, resource, both invocation modes, and the access note. No filler, nothing repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter read tool with no output schema, the description covers what the tool does and how to address it. However, with zero required parameters an agent could call it with no identifiers, and the description never states that one resolution route must be supplied or what a successful resolution yields.

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 the baseline is 3; the description nevertheless adds the mutual-exclusion/grouping logic between uid and the gtin+serial pair that the schema only hints at per-field. It does not clarify that at least one identifier set is effectively required despite zero required parameters.

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?

States a specific verb ('resolve') and specific resource ('EU ESPR Digital Product Passport'), plus the two supported resolution routes (GS1 Digital Link gtin+serial, or uid). This is clearly distinguishable from the sibling tools, which are all carbon-accounting/calculation tools.

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?

Explicitly gives the two invocation paths and the pairing rule (gtin together with serial, or uid alone), which is the main routing decision an agent faces. It does not state exclusions or what to do if both paths are supplied, so it falls short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.