Skip to main content
Glama

BRAINIAC E-commerce Catalog Intelligence

Validate product variants

ecommerce-catalog_product-variant-validate

Group products by the supplied parent sku and flag repeated color and size pairs, price disagreements, and parents that are not in the request. Missing options are not invented. Price $0.04 USDC. POST /api/v1/ecommerce-catalog/product-variant-validate. Unpaid calls return 402 and do not run.

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": "ecommerce-catalog_product-variant-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
productsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description does meaningful work: it discloses the $0.04 USDC cost, the POST endpoint, and the payment failure mode (402 and no execution). The 'missing options are not invented' line signals non-fabricating behavior. It still omits whether the call has any side effects and gives no hint about the response shape, which matters since there is no output schema.

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?

Purpose is front-loaded, then the concrete checks, then commercial/transport facts. Sentences are short and mostly earn their place; the endpoint path is largely redundant with the tool name but is a minor cost.

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 validation tool with no output schema, the description should indicate what the result contains (flags per product?) and how to choose an input format. It covers the checks and the billing model well but leaves the caller guessing on input mode and return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Four top-level parameters exist (csv, json, file, products) with 0% schema description coverage and nested product objects, yet the description explains none of them. It mentions 'parent sku' as a grouping key, which maps to a nested field, but says nothing about the four alternate input modes, their mutual exclusivity, or precedence — the single biggest ambiguity for a caller.

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 ('validate') and resource ('product variants'), then enumerates the exact checks performed: grouping by parent sku, repeated color/size pairs, price disagreements, and orphaned parents. That detail makes it clearly distinct from the feed-validate and normalize siblings, though no sibling is named explicitly.

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?

The description implies usage (pre-publication consistency checking of variant groups) and the line 'Missing options are not invented' hints that this is a reporting-only pass. However, it never states when to choose this over product-feed-validate, nor any prerequisite such as having both parents and children in the payload.

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