Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_storefront_xray_composite

Inspects a storefront URL to expose its e-commerce platform, ad/analytics stack, payment options, structured data, and a Shopify catalog sample.

Instructions

[E-Commerce Intelligence] Storefront X-ray: platform, ad/analytics stack, payment options, structured data and Shopify catalog sample Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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": "caelara_ecom_storefront_xray_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesStorefront URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

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 carries the full burden, and it does add real context: measured p50/p95 latency against a dated benchmark source and the backing endpoint domain. It does not state that the operation is non-mutating, whether any auth or quota applies, or how failures (unreachable store, bot-blocked storefront) are reported.

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 tool's capability list, then the benchmark and endpoint as a compact trailing note; no filler sentences. The bracketed category prefix and vendor benchmark citation are slightly promotional but still informative rather than wasteful.

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

Completeness4/5

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

For a one-parameter read-only scan with no output schema and no annotations, the description covers the important gap by enumerating the returned sections, plus latency expectations. Remaining gaps are minor: granularity of the Shopify catalog sample, response size, and error behavior.

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?

Schema description coverage is 100% for the single required parameter, so the schema already defines 'url' as the Storefront URL. The description adds no format or constraint detail beyond that, e.g., whether a bare domain is accepted or a full https URL is required. Baseline 3 applies when the schema does the work.

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?

Names a specific resource (storefront) and enumerates exactly what the scan surfaces: platform, ad/analytics stack, payment options, structured data, and a Shopify catalog sample. This distinguishes it from narrower siblings such as caelara_ecom_ad_pixel_detector or caelara_ecom_shopify_feed_extractor by implication, but never names an alternative 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?

Usage is only implied: the enumerated output set suggests a broad first-pass site profile, which is the kind of context that would select it over the single-signal siblings. There is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g., whether the URL must be public or reachable).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools