Skip to main content
Glama
Sign In

Fudge for Shopify

by ai.fudge
OverviewDiscussionsAdmin

Get audit result

get_store_audit_result
Read-onlyIdempotent

Read the latest run of one free diagnostic: status, report link and, once complete, the score and top fixes. Reading starts nothing. waitSeconds waits up to 50 seconds for a running report.

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": {
      "audit": "<audit>"
    },
    "name": "get_store_audit_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
auditYesThe diagnostic’s id.
storeNoThe connected store to use. Omit when only one is connected.
domainNoThe Shopify storefront to check, e.g. example.com. Required until a store is connected; afterwards, omit it to use a connected store.
waitSecondsNoDefault 0.

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 readOnlyHint, idempotentHint and non-destructive, so the description's job is lighter, yet it adds real behavior: reading triggers no new run, and waitSeconds blocks up to 50 seconds for a running report. It also sketches the return payload (status, link, score, fixes), which annotations cannot convey.

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?

Three short sentences, front-loaded with the resource and the returned fields, then the no-side-effect note, then the polling caveat. Nothing is redundant and the highest-value constraint comes first.

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 no output schema, the description carries the return-value burden and does so adequately by naming the four result components. What remains unstated is how a diagnostic is started and how the three audit ids differ, minor gaps for a read-only polling tool.

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 the baseline is 3, but the description genuinely enriches waitSeconds by explaining it waits for a running report rather than merely being an integer defaulting to 0. The audit enum, store and domain parameters are left entirely to the schema.

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: 'Read the latest run of one free diagnostic', and enumerates what is returned (status, report link, score, top fixes). 'Latest run' and 'reading starts nothing' implicitly separate it from listing audits and from running one, but no sibling is named 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: 'reading starts nothing' plus the waitSeconds polling behavior tell an agent this is for checking an already-started diagnostic. It never says when to prefer this over list_store_audits, or that an audit must first be started elsewhere, leaving the entry condition to inference.

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