Skip to main content
Glama

BRAINIAC E-commerce Catalog Intelligence

Validate a product feed

ecommerce-catalog_product-feed-validate

Check brainiac-catalog-v1 or the documented Google Merchant subset, plus any required fields and types in the caller schema. Unknown columns are ignored. Price $0.05 USDC. POST /api/v1/ecommerce-catalog/product-feed-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-feed-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
schemaNo
productsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description does useful work: it discloses lenient behavior ('Unknown columns are ignored'), cost ($0.05 USDC), and payment failure semantics (402 and no execution). It omits the key behavioral unknown, whether validation returns all errors or halts on the first, and gives no sense of the response shape despite there being 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?

The description is short and front-loads the validation scope before the operational details. The endpoint and payment sentences are arguably administrative but are compact and each carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with nested objects, five loosely documented parameters, no annotations, and no output schema, yet the description covers only the validation rules and billing. Missing are input-mode selection guidance and any indication of what a result contains, leaving real gaps for a caller with no structured fallback.

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 five top-level parameters, and the description only gestures at one of them ('the caller schema'). It never explains the relationship between csv, file, json, and products — for example whether they are mutually exclusive input modes or can be combined — which is the single most important thing an agent needs to form a valid call.

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 states a concrete check ('Check brainiac-catalog-v1 or the documented Google Merchant subset, plus any required fields and types') against a named resource, which is enough to distinguish a validator from sibling tools like product-normalize. It stops short of explicitly contrasting with ecommerce-catalog_product-variant-validate.

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 statement of when to call this versus the sibling validators or the normalize tool, nor any prerequisite such as feed size or format constraints. The agent must infer that this is a pre-ingest gate from the word 'Validate' alone.

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