Skip to main content
Glama

StoreTechScan — Ecommerce Tech Stack & ICP

Get 2026 Ecommerce Tech & Rate-Limit Benchmark

get_ecommerce_benchmark_2026
Read-onlyIdempotent

Retrieve empirical benchmark findings across 235 deduplicated real storefronts comparing unpaced burst HTTP (29.4% reachability, 155 HTTP 429s) vs. paced inspection (92.8% reachability, 95.9% cohort consistency, 100% zero-drift native-currency price medians). Costs 0 credits.

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

Input Schema

NameRequiredDescriptionDefault
formatNoReturn structured JSON summary ("summary", default) or include raw CC BY 4.0 CSV ("csv").

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds two genuinely new facts: the call is free (0 credits) and the results come from a fixed empirical study of 235 storefronts rather than a live crawl. However, the dense statistics about reachability and 429 counts describe the study's content rather than the tool's runtime behavior, and nothing is said about response size or latency.

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?

One sentence, verb-first, no filler. The embedded statistics are more detailed than strictly necessary to choose the tool, but they do tell the agent what the dataset contains, so they are not pure padding.

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?

This is a low-complexity tool with one optional parameter, and the annotations fully cover the safety profile. The gap is that there is no output schema, so the description should say what the 'summary' JSON actually contains (which metrics, at what granularity); instead it only lists headline figures from the study, leaving the agent to guess the response shape.

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 coverage is 100% and the single optional enum parameter is fully documented in the schema, including the default and what each value returns. The description says nothing about the format parameter, so it adds no meaning beyond the schema — 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 names a specific verb and resource — 'Retrieve empirical benchmark findings' over 235 deduplicated storefronts — so an agent knows this returns a static dataset rather than live inspection output, which implicitly separates it from get_inspection_results and inspect_domains. It stops short of explicitly naming a sibling or stating the boundary condition, so it is clear but not fully differentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The 'Costs 0 credits' line is a useful selection signal against paid siblings like check_credits, but the agent must infer that this tool is for background/contextual benchmark data rather than per-domain analysis.

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