Skip to main content
Glama

BRAINIAC E-commerce Catalog Intelligence

Check product description quality

ecommerce-catalog_product-description-quality-check

Flag missing, placeholder, HTML, and very short descriptions. When minLength is omitted, descriptions shorter than 40 characters are flagged. No description text is generated. Price $0.03 USDC. POST /api/v1/ecommerce-catalog/product-description-quality-check. 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-description-quality-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
productsNo
minLengthNo
maxTitleLengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/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 well: it discloses the 40-character default when minLength is omitted, states that no text is generated, names the price ($0.03 USDC), the HTTP method/path, and that unpaid calls return 402 without running. Undisclosed are how the flags are returned and what counts as a 'placeholder' description, which keeps it from a 5.

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 defect list and the minLength default are correctly front-loaded and terse, but the pricing, endpoint path, and 402 boilerplate consume roughly half the text without helping an agent choose or shape the call.

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?

For a nested-schema tool with six optional parameters, no output schema, and no annotations, the description does not cover the input-shape choice (single payload vs CSV/JSON file vs product array) or what the response contains. Only one of six parameters is addressed, leaving the definition under-specified relative to its complexity.

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 six parameters, and the description explains only minLength's default threshold. The mutually exclusive input channels (csv, json, file, products), the constraints on each, and especially maxTitleLength — which has no obvious role in a description-quality check — are left entirely unexplained.

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 and resource ('Flag ... descriptions') and enumerates the defect classes it detects (missing, placeholder, HTML, too short), which lets an agent distinguish it from the close sibling product-health-report. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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 line 'No description text is generated' implicitly rules out using this as a copywriting tool, and the flag categories imply when to reach for it. There is no explicit when-to-use vs when-to-use-another-tool statement, so usage is only implied.

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