Skip to main content
Glama

BRAINIAC E-commerce Catalog Intelligence

Report product catalog health

ecommerce-catalog_product-health-report

Combine the normalize, attribute, variant, description, category, feed, and image checks. The report does not approve the catalog for a sales channel. Price $0.12 USDC. POST /api/v1/ecommerce-catalog/product-health-report. 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-health-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
schemaNo
productsNo
taxonomyNo
minLengthNo
maxTitleLengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight: it discloses the $0.12 USDC cost, the POST endpoint, and that unpaid calls return 402 without running — genuinely useful for an agent. But it says nothing about the report's contents (per-check pass/fail, findings, scores) or how the csv/file/json/products inputs interact, which is significant for a tool with 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?

Front-loaded with the aggregation scope, followed by the scope disclaimer, price, endpoint, and payment failure mode. Four short sentences with no filler, though the endpoint and price lines are somewhat telegraphic.

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 complex aggregator with 8 nested parameters, no annotations, and no output schema, the description covers cost, transport, and failure semantics well but leaves both the input contract and the return shape unexplained. It is adequate for identifying the tool but not for invoking it correctly on the first try.

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?

Schema description coverage is 0% across 8 parameters, several of them deeply nested (file, schema.fields, products, taxonomy), so the description must compensate — and it does not. It mentions none of the inputs, leaving the relationship between csv, json, file, products, and taxonomy entirely undocumented.

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?

The description states a specific verb and resource ('health report') and explicitly enumerates the seven sibling checks it aggregates (normalize, attribute, variant, description, category, feed, image), which maps directly onto the sibling tool list. An agent can immediately tell this is the composite wrapper rather than any single check.

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?

Listing the combined checks implies the aggregation use case, and the 'does not approve the catalog for a sales channel' line usefully bounds expectations. However, it never explicitly says when to prefer this over calling the individual check tools, nor what preconditions the inputs must satisfy.

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