Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Ask to allow previews

show_preview_consent
Read-onlyIdempotent

Ask the merchant, with a card, whether new products and collections in a draft may be previewed by direct link on their live store. Use when a result says previewing needs their consent.

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": {
      "draft": "<draft>"
    },
    "name": "show_preview_consent"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYesThe draft’s fudge://project/… ref.
storeNoThe connected store to use. Omit when only one is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the interaction surfaces as a card shown to the merchant, and the scope of the consent is limited to direct-link preview of draft products and collections on the live store. It stops short of saying whether the answer is returned or whether consent persists once given.

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 sentences, no filler, with the action stated first and the invocation trigger second. Every clause carries information an agent needs.

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 two-parameter consent prompt with full schema coverage and no output schema, the description covers what it does, on what scope, and when to call it. The remaining gap is what happens after the merchant responds — whether the consent is recorded and what is returned — which would matter for sequencing the next step.

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 both parameters are already documented (draft ref, optional store). The description clarifies what the draft contains (new products and collections) and that the target is the live store, but adds no syntax or format detail beyond the schema, which is the baseline 3 case.

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?

Specific verb and object: it asks the merchant, via a card, whether draft products and collections may be previewed by direct link on the live store. This contrasts with a sibling like set_preview_consent (asking vs. setting), though the sibling is not named explicitly, so differentiation is implied rather than stated.

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 concrete trigger: 'Use when a result says previewing needs their consent.' That is a clear condition for invocation. It does not state any when-not condition or what to do if the merchant declines.

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