Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

product_intel_composite

Product page intelligence: JSON-LD product, GTIN validation, SKU normalization, review sentiment, ad pixels and price signals

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "product_intel_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesProduct page URL

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?

No annotations are supplied, so the description carries the full burden. It implies a remote fetch-and-extract operation but does not disclose whether it is read-only, what happens on non-product pages or blocked/JS-rendered pages, whether missing signals (e.g. no GTIN) cause errors or are omitted, or whether the call is slow/expensive. The enumeration of analyses is the only behavioral signal offered.

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?

A single short sentence with zero filler and the core scope front-loaded. It is however a bare fragment without a verb, and a few words noting that it combines per-signal checks would cost little and add much.

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 multi-analysis composite with no output schema and no annotations, so the description is the only place an agent could learn what the response looks like, how signals are grouped, or how partial failures are reported. None of that is covered, leaving a significant gap for a tool of this complexity.

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?

There is a single required URL parameter with 100% schema description coverage, so the schema already explains it fully. The description adds no syntax or validation detail beyond 'product page', so the baseline 3 applies.

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 enumerates the specific signals the tool extracts (JSON-LD product, GTIN validation, SKU normalization, review sentiment, ad pixels, price signals) from a product page, so an agent knows the resource and scope. It is a noun-phrase feature list rather than a verb-led statement, and it never states how it relates to the many single-purpose siblings, but the 'composite' framing plus the enumeration is enough to distinguish it as the all-in-one option.

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?

No when-to-use or when-not guidance is given. Given that siblings like jsonld_product_parser, gtin_upc_validator, sku_normalizer, review_sentiment_parser and ad_pixel_detector each cover one of the listed signals, an agent is left to infer whether this composite tool replaces those calls or supplements them, and there is no guidance on cost trade-offs of one broad call versus several narrow ones.

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