Skip to main content
Glama

AgenticCart: AI readiness checks for online stores

Validate a Google Merchant Center feed

check_merchant_feed
Read-onlyIdempotent

Validate a product feed against the Google Merchant Center product specification. Takes the feed URL (XML or JSON) and returns a 0-100 score with findings on required attributes, price formatting, availability values and GTIN checksums. Use this when asked to check, debug or validate a Google Merchant / Google Shopping feed, or to explain why products might be disapproved.

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_merchant_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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the tool fetches a remote feed and returns a 0-100 score plus findings grouped into four check categories, which tells the agent what to expect back. It does not mention what happens on an unreachable URL, non-conforming XML, or very large feeds, which keeps it off a 5.

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?

Two sentences, both front-loaded with the verb and resource first, then the return shape, then the trigger conditions. No filler and no repetition of the title.

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?

For a one-parameter, read-only validation tool with no output schema, the description supplies everything needed: what is validated, what the return looks like (score plus categorized findings), and when to reach for it. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100% and there is a single required parameter, so the schema already carries the semantics. The description's 'feed URL (XML or JSON)' restates what the schema property says almost verbatim, adding no new constraint or format detail. Baseline 3 is appropriate.

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 ('validate') and a specific resource ('a product feed against the Google Merchant Center product specification'), then names the concrete outputs (0-100 score, findings on attributes, price formatting, availability, GTIN checksums). The Google Merchant Center scoping is specific enough to separate it from check_acp_feed or check_store_readiness without opening schemas.

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?

Explicitly gives triggering conditions: 'when asked to check, debug or validate a Google Merchant / Google Shopping feed, or to explain why products might be disapproved.' That covers both the diagnostic and explanatory use cases. It stops short of a when-not or a named alternative for other feed standards, so it is clear context rather than full routing 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