Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

sku_normalizer

Normalize SKUs into canonical, compact and match-key forms

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

Input Schema

NameRequiredDescriptionDefault
skuNoSingle SKU string
skusNoArray of SKU strings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 burden and does not say whether output is deterministic, whether invalid or already-canonical SKUs are passed through or rejected, whether duplicates are collapsed in the array input, or what shape the three forms take. Only the bare transformation is disclosed.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though the terseness edges into under-specification rather than ideal conciseness.

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?

The tool is simple (2 optional params, no nesting, no output schema), but because there is no output schema the description should define what 'canonical', 'compact' and 'match-key' actually return. It names them without explaining them, leaving a meaningful gap for an agent that must interpret or present the result.

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 the single-vs-array distinction between 'sku' and 'skus' is already documented in the schema. The description adds no semantics about how the two inputs interact (precedence, mutual exclusivity, per-item error handling) and does not tie the three output forms to any parameter.

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 gives a specific verb (normalize) and resource (SKUs) and names three output forms (canonical, compact, match-key). An agent can tell this is a formatting/canonicalization utility, though the three form names are unexplained jargon and no sibling (e.g. gtin_upc_validator) is referenced for differentiation.

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?

There is no when-to-use guidance, no mention of when normalization is inappropriate (e.g. validation belongs to gtin_upc_validator), and no statement about which form to request or whether all three are returned. The agent must guess the intent entirely.

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