Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_sku_normalizer

Normalize single or bulk SKUs into canonical, compact, and match-key forms to standardize e-commerce product identifiers for matching and deduplication.

Instructions

[E-Commerce Intelligence] Normalize SKUs into canonical, compact and match-key forms Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
skuNoSingle SKU string
skusNoArray of SKU strings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only supplies latency benchmarks and the backing endpoint, not the traits an agent needs: whether the operation is read-only and deterministic, what normalization rules apply (case, whitespace, separators), and what happens to unparseable SKUs. The latency and endpoint details are useful provenance, but they are not core behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and efficient, but the benchmark citation, the benchmark date, and the endpoint URL are promotional padding that competes with the functional statement, and the sentences run together without punctuation.

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 two-parameter normalizer with no output schema, the description should at minimum explain the three output forms and the single-versus-batch input contract. It names the forms but leaves their meaning undefined and says nothing about the response shape, so the definition is marginally adequate rather than complete.

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%, so both parameters are already documented, and the description adds nothing about whether 'sku' and 'skus' are mutually exclusive or can be combined, nor about array-size limits. Baseline 3 applies because the schema carries the parameter explanation.

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?

The description uses a specific verb and resource, 'Normalize SKUs', and names the three output forms (canonical, compact, match-key), so an agent can distinguish this from siblings such as caelara_ecom_gtin_upc_validator. It never explicitly contrasts with those siblings, so the score stops short of a 5.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance: it does not say when to prefer normalization over GTIN/UPC validation or the JSON-LD product parser, nor does it say when normalization is a prerequisite for another step. It also gives no guidance on choosing between the single 'sku' and batch 'skus' inputs.

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

Deploy Server

Other Tools