Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

storefront_xray_composite

Storefront X-ray: platform, ad/analytics stack, payment options, structured data and Shopify catalog sample

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

Input Schema

NameRequiredDescriptionDefault
urlYesStorefront URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral burden. It does add useful context by disclosing the categories of information collected, including a Shopify catalog sample, which suggests inspection rather than mutation. It does not disclose operational traits such as whether it renders JavaScript, whether the URL must be public, rate limits, or whether any authentication is required.

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 a single compact phrase with no filler, and the key scope is front-loaded immediately after the tool name. It is slightly cryptic because it is a label-style fragment rather than a sentence, but it remains efficient and scannable.

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 no-annotation, no-output-schema composite tool, the description gives an adequate high-level inventory of what it inspects. It remains incomplete regarding scan depth, output structure, URL constraints, and performance or failure behavior, which matter for a multi-signal storefront inspection tool.

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?

The schema has 100% description coverage for the single url parameter, so the schema already explains that it expects a storefront URL. The description adds no further parameter semantics, such as whether the URL must be a full page URL or whether subdomains matter, so the baseline of 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 identifies a storefront inspection tool and enumerates the specific signals it covers: platform, ad/analytics stack, payment options, structured data, and a Shopify catalog sample. Although it is phrased as a label rather than a verb-led sentence, the scope is specific enough to distinguish it from narrower siblings such as ad_pixel_detector or jsonld_product_parser.

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 composite nature and the listed categories imply that this is the broad overview tool for a storefront URL, while the siblings appear to be narrower extractors or detectors. However, the description does not explicitly state when to use this tool versus those alternatives, nor does it mention any exclusions or prerequisites.

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