Skip to main content
Glama

map_product_to_dpp

Read-onlyIdempotent

Use this tool when a user has product information in ANY form (a pasted product sheet or label text, a CSV export with a header row, or loose JSON) and wants to know how it maps to EU Digital Product Passport fields for textiles. Returns the mapped fields with where each came from, a readiness score, the missing mandatory fields with how to obtain each one, and a GTIN check. Up to 200 rows. Deterministic, never invents data, 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": "map_product_to_dpp"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNoCSV/TSV/semicolon text with a header row; one product per row.
textNoFree-text product sheet or label (key: value lines, '62% cotton', 'Made in Portugal'...).
productNoOne product object with any keys (Shopify export, PIM row...).
productsNoSeveral product objects.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description still adds real value beyond them: it discloses the return contents (provenance per field, readiness score, missing mandatory fields with remediation, GTIN check), the 200-row cap, and that it is deterministic and never fabricates data. It does not say what happens when multiple input parameters are supplied at once, which is the main behavioral gap.

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?

Four dense sentences, front-loaded with the trigger condition and followed by the return contract, limits and guarantees. Nothing is redundant with the schema, though the final sentence is a four-item grab bag that reads slightly like a feature checklist rather than prose.

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?

An output schema exists, so the description need not detail return values, and it is complete on determinism, row limits and no-account requirement. However, it leaves ambiguity about whether the four input parameters are mutually exclusive or additive, which matters for a tool with four optional, nested-object inputs and only one row cap mentioned.

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?

With 100% schema coverage the baseline is 3, but the description earns an extra point by tying the visible input modes to the parameters: 'pasted product sheet or label text', 'CSV export with a header row', and 'loose JSON' make it clearer which of text/csv/product/products to populate. The 'up to 200 rows' note also anchors the products array limit.

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+resource: maps product information in any form to EU Digital Product Passport fields for textiles. It explicitly enumerates the accepted input forms (pasted sheet/label text, CSV with header row, loose JSON), so an agent knows exactly what job this tool performs.

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?

Opens with an explicit trigger: 'Use this tool when a user has product information in ANY form ... and wants to know how it maps to EU DPP fields.' That is a clear when-to-use condition. It stops short of naming a when-not-to-use case or pointing to the adjacent readiness/requirements siblings, so it falls just below the top band.

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