Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Record a store change

record_change

Add a change made outside Fudge to the store’s timeline, such as ads, prices, apps, email, shipping or theme edits in Shopify, so later results can be attributed. Fudge’s own publishes are recorded automatically.

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": {
      "what": "<what>",
      "surface": "<surface>"
    },
    "name": "record_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoWhen it took effect: YYYY-MM-DD or an ISO timestamp. Defaults to now.
whyNoIntent or expected effect, so results can be checked against it later.
whatYesWhat changed, concretely, e.g. "Raised Meta prospecting budget from €50 to €80 a day".
linksNofudge:// references or Shopify GIDs of what the change affected, e.g. gid://shopify/Product/123.
storeNoThe connected store to use. Omit when only one is connected.
surfaceYesWhere: theme, catalogue, pricing, discounts, email, Meta ads, Google ads, apps, shipping or other.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds real context beyond them: this appends to a persistent timeline whose purpose is downstream attribution ('so later results can be attributed'), which explains why accuracy of the entry matters. It does not warn that repeated entries create duplicates despite non-idempotency, nor mention permissions.

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 tight sentences, front-loaded with the action and its purpose, with the exclusion clause at the end where it belongs. Nothing is redundant or padded.

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 6-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, scope, and the attribution rationale well. It omits what a successful record returns and how duplicate or retroactive entries are handled, which are minor gaps given the rich schema.

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 every parameter is already documented with examples and formats in the schema. The description's surface examples ('ads, prices, apps, email, shipping or theme edits') merely mirror the schema's own surface description and add no new syntax or constraint information. Baseline 3 applies.

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 — 'Add a change ... to the store's timeline' — plus concrete examples of what counts (ads, prices, apps, email, shipping, theme edits). It also draws a clear boundary by noting that Fudge's own publishes are recorded automatically, so an agent can tell this is for out-of-band changes only.

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?

Gives a clear when-to-use condition ('a change made outside Fudge') and an implicit when-not ('Fudge's own publishes are recorded automatically'), which prevents duplicate logging. It does not name any sibling tool as an alternative, so it falls short of the top band but leaves no real ambiguity about applicability.

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