Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Run Knowledge Base check

run_knowledge_base_check

Run Fudge’s free Shopify Knowledge Base report: 15 shopper questions with the exact answers, gaps and conflicts with published information. Takes 2–5 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_knowledge_base_check"
  }
}

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.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), it discloses run duration (2–5 minutes), a bounded wait (up to 45 seconds), and 24-hour result caching keyed to `fresh`. What is missing is the follow-up behavior when "a run in progress" is returned — no instruction on whether to re-poll or how.

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 deliverable front-loaded and no filler. The "waits up to 45 seconds" clause is slightly ambiguous against the stated 2–5 minute run time, costing a little clarity.

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?

For an async, open-world, non-idempotent operation with no output schema, the description sketches the result content but not its shape or how to obtain a completed result once an in-progress run is returned. The critical calling details are present, but the async lifecycle is only half covered.

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 coverage is 100%, so all three parameters are already documented in the schema, including the `fresh` cache-bypass semantics. The description restates the 24-hour cache behavior but adds no syntax or interaction detail (e.g., whether `store` and `domain` can be combined) beyond what the schema provides.

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 ("Run ... Shopify Knowledge Base report") and enumerates the deliverable: 15 shopper questions with exact answers, gaps, and conflicts. This clearly separates it from siblings like run_ai_readiness_check and run_catalog_data_audit.

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 is only implied: you run this to get the KB report, and the domain/store prerequisites are partially stated ("Required until a store is connected"). There is no explicit when-not or comparison against the other run_* check tools, leaving the agent to infer the choice.

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