Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Draft preview

show_draft
Read-onlyIdempotent

Show a Fudge draft in the side panel with its screenshot, saved time, change count and links. Without a ref, lists recent drafts.

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": "show_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoA fudge://project/… ref.
storeNoThe connected store to use. Defaults to the first one.

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 already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, by disclosing that output is a visual side-panel preview containing screenshot, timestamp, change count and links. The dual behavior with and without a ref is also disclosed, which genuinely matters for the caller. Minor gaps remain around permissions or what happens with an invalid ref, but that is above the bar set by the annotations.

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 short sentences with zero filler; the primary behavior is front-loaded and the fallback mode follows immediately. Every clause carries information an agent would otherwise have to guess.

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 simple, read-only preview tool with fully documented parameters and complete annotations, the description covers purpose, output content, and both calling modes. Only the ref format and error behavior are unaddressed, and the schema already supplies the ref format, so nothing essential is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining the consequence of omitting ref (recent drafts are listed instead) — a default-behavior semantic the schema only hints at with an optional field. The store parameter is left entirely to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ("Show a Fudge draft") plus where it appears ("in the side panel") and what it renders (screenshot, saved time, change count, links). The no-ref fallback is also spelled out, so the agent knows the tool has two modes. It never names a sibling such as read_draft_file or search_draft_files to sharpen the boundary, which keeps it out of 5 territory.

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?

"Without a ref, lists recent drafts" is conditional guidance, but it is about how to drive this tool's own parameter rather than when to pick it over alternatives. There is no statement of when an agent should prefer this preview over reading draft files or searching drafts. Usage is implied by the description of the panel view rather than argued.

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