Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Ecommerce platform detect

web-technology_ecommerce-platform-detect
Read-onlyIdempotent

Classify the ecommerce platform from technology detection results in the Ecommerce category. Price $0.03 USDC. POST /api/v1/web-technology/ecommerce-platform-detect. An unpaid call returns the x402 payment terms and does 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": "web-technology_ecommerce-platform-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNourl, string, length 0 to 2000. Optional.
htmlNohtml, string, length 0 to 2097152. Optional.
metaNometa, object. Optional.
cookiesNocookies, array. Optional.
headersNoheaders, object. Optional.
scriptUrlsNoscriptUrls, array. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
evidenceNoevidence. Array.
platformNoplatform. String.
confidenceNoconfidence. Number.
limitationsNolimitations. Array.
alternativesNoalternatives. Array.

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 readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely useful non-annotated context: the $0.03 USDC price and the x402 payment gate where an unpaid call returns payment terms instead of executing. It does not discuss rate limits, failure modes, or what the classification returns, so it is additive but not rich.

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?

Three short, front-loaded sentences: purpose, price, endpoint, then the payment caveat. Nothing is redundant, though the endpoint and price could be ordered more logically relative to the purpose statement.

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?

With an output schema present, return values need not be explained, and the schema fully documents the six inputs. What remains missing is sibling differentiation and any hint about how the raw inputs are used for classification, which matters for a tool whose name overlaps several siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with 6 optional parameters fully documented inline, so the schema carries the parameter burden. The description adds no per-parameter detail and in fact gestures at a different input shape ("technology detection results") than the raw crawl inputs the schema accepts.

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 ("Classify the ecommerce platform") plus the category scope (Ecommerce) and the endpoint, which separates it from generic siblings like technology-detect or payment-provider-detect. The phrase "from technology detection results" is slightly at odds with the schema, which accepts raw url/html/headers/cookies/scriptUrls rather than a detection-result payload, leaving minor ambiguity about what the input actually is.

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 guidance on when to choose this over sibling tools such as web-technology_technology-detect or web-technology_payment-provider-detect, and no statement of prerequisites or expected input state. The only conditional given is the payment one (unpaid calls return terms and do not run), which is billing behavior, not usage guidance.

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