Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Get saved findings

get_store_insights
Read-onlyIdempotent

Read the findings and recommendations Fudge has saved for this store, most important first; narrow by area, subject, kind, date or text. With ref, one record in full with its sources and measurements. An empty list means nothing is saved yet. This never starts an investigation.

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

Input Schema

NameRequiredDescriptionDefault
refNoRead one record in full; the other filters are ignored.
areaNoseo, ai-discovery, conversion or merchandising, or a library such as landing-pages or quizzes.
kindNo
limitNo
queryNoWords to find in the title, summary or body.
sinceNoOnly records created or updated on or after this date.
storeNoThe connected store to use. Omit when only one is connected.
subjectNoA product, collection, page or article ID (product-42 or a Shopify GID), or a Fudge Plan ref.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description still adds real context: result ordering by importance, the meaning of an empty result ('nothing is saved yet'), the extra payload in ref mode ('its sources and measurements'), and the explicit no-side-effect guarantee. It omits pagination/truncation behavior relative to the limit parameter.

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?

Front-loaded with the core action, then the filter list, then the ref special case, then the empty-state and no-side-effect caveats. Every clause carries information; there is no restatement of the title or filler.

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 an 8-parameter, zero-required read tool with no output schema, the description covers what comes back in both modes, ordering, and the empty case. The remaining gap is limit/pagination semantics — an agent cannot tell whether a capped list means there are more records.

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 75%, so most parameters are already documented. The description adds meaning where the schema is silent: 'most important first' explains what limit actually returns (top-N by importance), and it ties area/subject/kind/since/query into a single narrowing concept. It does not explain how multiple filters combine (AND vs OR) beyond the ref case.

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 ('Read the findings and recommendations'), the scope ('for this store'), the ordering ('most important first'), and a mode switch ('With ref, one record in full'). The closing 'This never starts an investigation' separates it from the investigation/plan-starting siblings without naming them.

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 clear when-to-use guidance: list mode with narrowing filters by area, subject, kind, date or text, versus ref mode for a single full record. It also supplies a when-not signal ('never starts an investigation'). It does not name a specific alternative tool to use instead when the agent wants an investigation, so it stops short of a full 5.

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