Skip to main content
Glama

AgenticCart: AI readiness checks for online stores

Grade a feed against the Agentic Commerce Protocol

check_acp_feed
Read-onlyIdempotent

Grade a product feed against the Agentic Commerce Protocol (ACP) / OpenAI product feed specification, which governs whether a catalog can be sold inside ChatGPT. Takes the feed URL (XML or JSON) and returns a 0-100 score plus per-attribute findings on required and recommended fields. Use this when asked whether a catalog or feed is ready for agentic commerce, for ChatGPT Instant Checkout, or for ACP compliance in general.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic URL of the product feed (XML or JSON).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description's job is to add context — and it does, by disclosing the output shape (0-100 score plus per-attribute findings on required vs. recommended fields) and accepted input formats. What is missing is any note on what happens with unreachable or malformed feed URLs, but the return-value disclosure is genuinely additive.

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?

Two sentences, front-loaded with the action and result, then the usage triggers. Tight and readable; only the redundant restatement of the XML/JSON input formats could be trimmed.

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 tool with no output schema, the description carries what an agent needs: what is graded, against which spec, what comes back, and when to reach for it. Only the sibling differentiation against check_merchant_feed / check_store_readiness is left implicit.

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 parameter at 100% schema description coverage, so the baseline is 3. The description's "XML or JSON" detail duplicates wording already present in the schema and adds no new constraint such as size limits, authentication requirements, or whether redirects are followed.

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?

"Grade a product feed against the Agentic Commerce Protocol" is a specific verb plus resource, and the scope (ChatGPT Instant Checkout / ACP compliance) is narrow enough to be separable from a generic feed check. It does not name or contrast with the near sibling check_merchant_feed, so the agent must infer the boundary from the protocol names alone.

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?

"Use this when asked whether a catalog or feed is ready for agentic commerce, for ChatGPT Instant Checkout, or for ACP compliance" gives concrete triggering conditions. It stops short of stating when not to use it, e.g. that plain merchant-center or Google Shopping validation belongs to a sibling tool.

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