Skip to main content
Glama

neuron

by io.github.conquext
OverviewDiscussionsAdmin

Update Storefront

neuron_update_storefront

Create or update the seller storefront (nestuge-style page). Handle is auto-generated from the display name if omitted.

Input Schema

NameRequiredDescriptionDefault
bioNoShort store bio
handleNoURL handle (a-z, 0-9, hyphens). Becomes /s/<handle>.
enabledNoWhether the storefront is public
socialsNoMap of social links e.g. { instagram: 'https://...' }
avatarUrlNo
brandColorNoHex brand colour e.g. #188A56. Also used for buttons and accents in buyers' delivery emails.
displayNameNoStore display name
replyToEmailNoWhere buyers' replies to delivery emails go. Null = the account owner's email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / brandColor / description
      Previous value: -"Hex brand colour e.g. #188A56"New value: +"Hex brand colour e.g. #188A56. Also used for buttons and accents in buyers' delivery emails."
    • addedInput schema / properties / replyToEmail
      Added value: +{
+  "anyOf": [
+    {
+      "format": "email",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Where buyers' replies to delivery emails go. Null = the account owner's email."
+}
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-readOnly, non-destructive, non-idempotent operation, so the safety profile is covered. The description usefully adds the upsert semantics (create OR update) and the handle auto-generation rule, which matters given idempotentHint=false, but omits auth requirements, what happens to fields not supplied, and overwrite behavior.

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, front-loaded with the core action followed by the one non-obvious default rule. No filler or repetition of structured data.

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

Completeness5/5

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

With eight optional parameters, a rich schema, and a mutation annotation profile, an agent has enough to call the tool correctly. No output schema exists, but the description covers the upsert nature and the one parameter default that isn't self-evident.

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 88%, so the schema already documents most parameters and baseline is 3. The description earns an extra point by adding the derivation rule that the handle is auto-generated from displayName when omitted, which is genuine behavioral meaning not present in 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?

The description states a specific verb ('create or update') and resource ('seller storefront'), correctly framing the tool as an upsert. It clearly distinguishes itself from neuron_get_storefront by the mutating verb, though it never names that sibling 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 only implied by the upsert framing; there is no explicit when-to-use guidance, no mention of the read-only sibling neuron_get_storefront, and no statement about prerequisites such as seller enrollment. An agent must infer context from the verb alone.

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

All neuron 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