Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Start draft

start_draft

Open a private Fudge draft to build in directly. Fudge copies the live theme into a draft with its own preview. Give a short title and the storefront page, or work to continue existing work. requestId makes retries create one draft. Use for precise changes you make yourself; needs a Fudge plan that includes building.

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": {
      "title": "<title>",
      "requestId": "<requestId>"
    },
    "name": "start_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoStorefront path the work is about, e.g. /products/blue-runner, /collections/sale or /pages/about. Anchors the preview. Defaults to the home page.
workNoA fudge://project/… ref to continue instead of starting new work.
storeNoThe connected store to use. Omit when only one is connected.
titleYesShort merchant-facing name for the work, e.g. “Size guide on product pages”.
requestIdYesA unique ID you choose for this request, e.g. a UUID. Retries reuse it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, it discloses the key side effect (the live theme is copied into a draft with a separate preview), the retry semantics tied to requestId, and the plan/entitlement prerequisite ("needs a Fudge plan that includes building"). These are exactly the behavioral facts an agent needs before calling a non-read-only, non-idempotent mutation.

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?

Five short sentences, front-loaded with purpose followed by mechanism, parameters, and usage condition. "Give a short title and the storefront `page`" mostly restates schema constraints, a minor redundancy, but nothing bloats the definition.

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 5-parameter mutation with full schema coverage and no output schema, the description covers purpose, side effects, prerequisites, and retry behavior well. The remaining gap is that it doesn't say what the call yields back (e.g., a draft reference to pass into edit_draft_file or show_draft), which would help the agent chain tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description still adds meaning: `page` anchors the preview and `work` continues existing work rather than starting fresh. Its most valuable addition is the retry contract for `requestId`, which the schema only hints at with "Retries reuse it."

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 opens with a specific verb and resource ("Open a private Fudge draft to build in directly") and clarifies that the draft is a copy of the live theme with its own preview. It doesn't explicitly name or contrast with sibling builder-style tools, so an agent must infer the boundary from "precise changes you make yourself."

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 for precise changes you make yourself" and "or `work` to continue existing work" give clear selection context, and the plan requirement sets a prerequisite. There is no explicit when-not statement or named alternative, so the contrast with start_store_builder or start_website_redesign is implied rather than stated.

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