Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Edit store document

edit_store_document
Destructive

Change part of a store document, such as a Plan’s brief or the design guide, by replacing exact text. Fails if the text is gone or the document has changed since it was read.

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": {
      "path": "<path>",
      "old_string": "<old_string>",
      "new_string": "<new_string>"
    },
    "name": "edit_store_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath of the existing document.
storeNoThe connected store to use. Omit when only one is connected.
new_stringYesReplacement text; empty deletes old_string.
old_stringYesExact text to replace.
replace_allNoReplace every occurrence. Defaults to false.

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 declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the exact-text-match requirement and the stale-document failure mode ('the document has changed since it was read'), which tells the agent this is an optimistic-concurrency edit and why an edit might reject.

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, no filler, with the core purpose front-loaded and the failure condition as a short second sentence. Every clause carries information.

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 tool with full schema coverage and no output schema, the definition covers purpose, matching semantics and the key failure mode. What it omits – return value and any permission/scoping notes for the store parameter – are minor since the schema documents those inputs.

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 baseline is 3. The description adds meaning beyond the schema by framing old_string as an exact-text match and characterizing the target as part of a document rather than the whole thing, and by naming which kinds of documents (Plan brief, design guide) the path parameter points at.

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 gives a specific verb and resource ('Change part of a store document... by replacing exact text') and grounds it with concrete examples ('a Plan's brief or the design guide'). It is clearly an edit operation on an existing document, distinguishable from create_store_document and read_store_document, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: 'Change part of a store document' plus 'replacing exact text' tells an agent this is for surgical edits to existing documents, and the failure clause hints that a prior read is required. No explicit when-to-use/when-not guidance or named alternatives are given.

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