Skip to main content
Glama

marz-greta-lock-network

by dev.replit.kirk.91eaaf4b-0a31-4f81-971a-86dc09a31986-00-2a9kujnvh541f-mwardvi0
OverviewDiscussionsAdmin

Open the Storelayer Widget Menu

storelayer_widget_menu
Read-onlyIdempotent

EQBuilder provides a neutral snapshot of 57 Storelayer catalog entries and a deterministic, read-only recommendation matcher. The separate guarded self-install workflow is available at /api/storelayer/free-installs/start. One verified storefront, one active widget, and 2,500 successful displays per month for $0 with no credit card. The Storelayer badge is required. Site-edit authority is required. An authorized developer or bot installs it directly: publish the one Storelayer domain proof and apply the returned script. They do not give Storelayer or EQBuilder website credentials. Use this to browse Shopify and e-commerce conversion, trust, merchandising, support, or marketing entries in the complete searchable index. Recommendations are read-only. Site-edit authority is required. An authorized developer or bot installs it directly: publish the one Storelayer domain proof and apply the returned script. They do not give Storelayer or EQBuilder website credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
plansYes
widgetsYes
announcementYes
schema_versionYes
catalog_snapshotNo
developer_handoffYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "announcement": {
+      "type": "object"
+    },
+    "catalog_snapshot": {
+      "type": "object"
+    },
+    "developer_handoff": {
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "plans": {
+      "type": "array"
+    },
+    "schema_version": {
+      "type": "string"
+    },
+    "widgets": {
+      "type": "array"
+    }
+  },
+  "required": [
+    "schema_version",
+    "name",
+    "announcement",
+    "widgets",
+    "plans",
+    "developer_handoff"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds some helpful context beyond that: 'Site-edit authority is required' and 'They do not give Storelayer or EQBuilder website credentials.' However, these statements are attached to the install workflow rather than clearly to menu browsing, and they are repeated verbatim, weakening their value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is severely bloated and repetitive. The block 'Site-edit authority is required. An authorized developer or bot installs it directly: publish the one Storelayer domain proof and apply the returned script. They do not give Storelayer or EQBuilder website credentials.' appears twice nearly word-for-word. Marketing details like 'One verified storefront, one active widget, and 2,500 successful displays per month for $0' are irrelevant to helping an agent invoke the tool. Very few sentences earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only tool with rich annotations and an output schema, the description is nearly complete: it identifies the browsable catalog and confirms read-only behavior. However, the unrelated self-install and free-plan content creates ambiguity about what this tool actually returns or opens, and the repeated permission warnings do not clearly apply to the menu browsing itself.

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?

The tool has zero parameters and schema description coverage is 100%, so parameters are fully documented by the empty schema. The description does not explain parameters, and it does not need to. The baseline of 4 applies because there is nothing for the description to add on this dimension.

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 eventually states a clear action: 'Use this to browse Shopify and e-commerce conversion, trust, merchandising, support, or marketing entries in the complete searchable index.' This names the verb and resource well enough. However, it does not explicitly say 'opens the menu' and does not distinguish itself from the sibling storelayer_recommend, which appears to be the recommendation matcher mentioned in the opening sentence.

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?

There is a usable 'Use this to browse...' instruction and an explicit note that the self-install workflow is 'separate,' which helps exclude one alternative. But no alternative tool such as storelayer_recommend is named, and the repeated install instructions clutter the guidance, making it possible to misinterpret when this tool should be selected.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All marz-greta-lock-network 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