Skip to main content
Glama

AgenticCart: AI readiness checks for online stores

Check store AI readiness

check_store_readiness
Read-onlyIdempotent

Audit any public online store for AI and agent readiness. Takes the store homepage URL and returns a 0-100 score with concrete findings: whether AI crawlers are allowed in robots.txt, whether the pages send their content in the HTML or only build it in the browser with JavaScript (React, Vue or Angular apps that most AI crawlers see as empty), whether product structured data is present, sitemap, llms.txt and HTTPS. Use this when asked whether a shop can be discovered, read or cited by AI shopping assistants such as ChatGPT, Perplexity or Google AI Overviews, or when reviewing a store's AI visibility. Works on any store on the public web - no account, no ownership and no login required.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe store homepage URL, e.g. "https://example.com". A product or category URL also works; the analyzer resolves the site root from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so this is safe-read context. The description adds what annotations cannot: no account, ownership or login required, it operates on any store on the public web, and it explains the non-obvious detection behavior (JS-built pages appear empty to most AI crawlers). That is real value beyond the structured fields.

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 purpose, then the checks, then the usage trigger, then the access constraints. The list of checks is long but each item is meaningful; the parenthetical about React/Vue/Angular is slightly bulky yet earns its place by explaining why JS rendering matters.

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

Completeness5/5

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

No output schema exists, so the description correctly carries the return-value burden by stating it returns a 0-100 score with concrete findings across named dimensions. Combined with the access requirements and scope, an agent has everything needed to call it correctly.

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 parameter at 100% schema coverage, and the schema already documents the URL format and the 'product or category URL also works; the analyzer resolves the site root' behavior. The description adds no parameter meaning beyond that, so the baseline 3 for fully-covered schemas 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?

Opens with a specific verb and resource ('Audit any public online store for AI and agent readiness') and enumerates exactly what the audit covers: robots.txt, JS-rendered content, structured data, sitemap, llms.txt and HTTPS. An agent can tell this is the umbrella multi-signal audit rather than the narrower sibling checks, though it never names those siblings to make the distinction explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete triggering context: 'Use this when asked whether a shop can be discovered, read or cited by AI shopping assistants such as ChatGPT, Perplexity or Google AI Overviews, or when reviewing a store's AI visibility.' No when-not conditions or explicit routing to the narrower sibling tools (check_llms_txt, check_product), which is the remaining gap.

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