Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Start website redesign

start_website_redesign

Start Fudge’s free website redesign for a Shopify store, which generates three homepage concepts on Fudge’s website. Use when the merchant wants new design directions for their whole site. Returns a link for them.

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": {
      "domain": "<domain>"
    },
    "name": "start_website_redesign"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe Shopify storefront, e.g. example.com.
instructionsNoWhat the merchant wants from the redesign, in their words.

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 only say it is a non-read-only, non-idempotent, non-destructive, non-open-world call; the description adds that it is free, that it produces exactly three concepts, that generation happens on Fudge's website, and that the merchant receives a link. That is meaningful context for a mutating, externally-visible operation, though it does not say what happens on repeat calls or how long it takes.

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 short sentences, front-loaded with the action and followed by use case and return value. Minor redundancy between "on Fudge's website" and "Returns a link for them," but nothing wasteful enough to hurt comprehension.

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?

With no output schema, the description correctly states what the caller gets back (a link) and how many concepts are produced, which is the key missing piece otherwise. For a two-parameter async-style generation tool it is nearly complete, lacking only expectations about latency or re-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?

Schema description coverage is 100%, so the schema already documents both `domain` and `instructions` fully. The description alludes to the store domain and to the merchant's design wishes but adds no format, validation, or usage nuance beyond the schema. Baseline 3 applies.

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?

"Start Fudge's free website redesign for a Shopify store" pairs a specific verb with a specific resource, and adds concrete scope: three homepage concepts generated on Fudge's site for the whole store. The "whole site" framing implicitly separates it from page-level siblings, though no sibling is named outright.

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 when the merchant wants new design directions for their whole site" gives a clear triggering condition and the "whole site" qualifier steers agents away from page-scoped alternatives. There is no explicit when-not clause or named alternative, so it falls short of a 5.

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