Skip to main content
Glama

AgenticCart: AI readiness checks for online stores

Check a product page for AI readability

check_product
Read-onlyIdempotent

Audit a single product page for how well AI shopping assistants can read and recommend it. Takes the product page URL and returns a 0-100 score with findings on structured data (Product/Offer schema), price and availability markup, images, description quality and identifiers such as GTIN and brand. Use this for questions like "why does ChatGPT not recommend this product", or when reviewing one specific product listing rather than a whole store. Works on any public product page.

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_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full URL of one product page, e.g. "https://example.com/products/blue-shoe".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, open-world and non-destructive, so safety is covered. The description adds real value by disclosing the output shape (0-100 score with findings on structured data, price/availability markup, images, description quality, GTIN/brand) and that it works on any public page, though it says nothing about rate limits, failures, or crawl restrictions beyond "public".

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing work: purpose, output contract, and usage scope. Front-loaded with the audit statement and free of filler.

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 audit with no output schema, the description covers purpose, return contents and scope well. It could mention whether the page must be publicly crawlable or how the score dimensions are weighted, but nothing essential is missing for correct invocation.

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?

With a single parameter at 100% schema coverage, the schema already documents the URL with an example. The description reinforces that exactly one full page URL is expected ("single product page", "one specific product listing"), but adds no format or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Audit a single product page") plus the goal (how well AI shopping assistants can read and recommend it). The scope constraint "one specific product listing rather than a whole store" lets an agent distinguish it from store-level checks without opening the schema.

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 trigger ("why does ChatGPT not recommend this product") and an explicit when-not (reviewing a whole store). It stops short of naming the sibling tool that handles the store-level case, but the exclusionary condition is clear enough to route correctly.

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