Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Run catalog data audit

run_catalog_data_audit

Run Fudge’s free AI shopping catalogue report: categories, structured data, product details and whether buyer searches find the right products. Takes 2–4 minutes and waits up to 45 seconds. Returns a run in progress or a result from the last 24 hours unless fresh is true.

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

Input Schema

NameRequiredDescriptionDefault
freshNoStart a new run even when a result from the last 24 hours exists.
storeNoThe connected store to use. Omit when only one is connected.
domainNoThe Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-idempotent, non-destructive operation, and the description adds genuinely new behavior: 2-4 minute runtime, a 45-second wait ceiling, and that it may return either an in-progress run or a 24-hour cached result. It stops short of saying how a caller should poll or retrieve an in-progress run, which is the one behavioral detail an agent still has to guess.

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 tight sentences with the runtime and caching caveats front-loaded where they matter most for an agent's decision. The word "free" is the only marketing residue that does not contribute to correct invocation.

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

Completeness3/5

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

There is no output schema, so the description bears the burden of explaining the return value, and it only sketches it as "a run in progress or a result from the last 24 hours." For a long-running, non-idempotent operation it should say what the caller does next with an in-progress run, likely pointing at the result-fetching sibling.

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%, so the schema already carries the parameter definitions and the baseline is 3. The description restates the `fresh` behavior (24-hour cached result unless fresh is true), adding only mild reinforcement rather than new syntax, defaults, or format details for `store` and `domain`.

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?

The description names a specific verb and resource ("Run Fudge's free AI shopping catalogue report") and enumerates the checked dimensions: categories, structured data, product details, and search relevance. It is clearly distinct from generic siblings by being a full catalogue audit, though it never names the closely-related siblings (check_catalog_data, run_ai_readiness_check) to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage context is implied through the fresh/cached-result mechanics and the store-connection prerequisite for `domain`, but the description never states when to choose this over the sibling audit tools. An agent must infer that this is the heavy full-audit path versus the lighter check tools from the stated 2-4 minute runtime.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fudge for Shopify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources