Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Search draft files

search_draft_files
Read-onlyIdempotent

Find theme files in a Fudge draft. With pattern, search contents by regular expression; without it, list files matching paths globs.

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>",
      "paths": "<paths>"
    },
    "name": "search_draft_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYesThe draft’s fudge://project/… ref.
pathsYesFiles, folders or glob patterns, e.g. ["sections", "snippets/*price*.liquid"].
storeNoThe connected store to use. Omit when only one is connected.
patternNoRegular expression (RE2 syntax: no lookarounds or backreferences) to search for in those files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuine behavioral detail about the two modes, but says nothing about return shape, ordering, result limits, or what a non-matching glob or invalid regex yields, leaving gaps for a search tool.

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, and the mode split is front-loaded immediately after the purpose statement. Every clause carries information the agent needs to choose a call shape.

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 four parameters, 100% schema coverage, and a clear dual-mode description, an agent has enough to call this correctly, and annotations cover safety. The main omission is that no output schema exists and the description gives no hint about what results look like (file lists versus content matches), which is minor but noticeable for a search tool.

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%, and the schema already documents the `draft` ref format, `paths` glob examples, `store` omission when one store is connected, and RE2 syntax constraints. The description restates the `pattern`/`paths` interplay but adds no semantics beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 uses a specific verb and resource ("Find theme files in a Fudge draft") and then clearly splits the tool's two operating modes: content search with `pattern` versus path listing without it. It does not explicitly name sibling alternatives such as read_draft_file, so it falls short of full differentiation, but an agent can still understand what this tool does without reading the schema.

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?

The definition gives useful mode-selection guidance: pass `pattern` to regex-search contents, omit it to list files matching `paths` globs. However, it offers no guidance on when to reach for this tool instead of read_draft_file or edit_draft_file, and no exclusions or prerequisites are stated, leaving the tool-versus-alternative decision implied.

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