Skip to main content
Glama
Sign In
storefront-mcp

storefront-mcp

by cloudcart
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

learn_cloudcart_storefront

Call this before other storefront tools. It explains CloudCart Storefront API behavior schema alone omits: buyer authentication, checkout URLs, server-owned pricing, and cart keys.

Instructions

Call this first, before anything else in this server.

It returns a conversationId that every other tool here requires, and — more usefully — what the CloudCart Storefront API's schema does not show: how a signed-in buyer is sent (an argument or @inContext(buyer:), never an Authorization header), that a Nitrogen storefront's checkout is the store's own (cart.checkoutUrl), that the server owns every price and money is shown as formatted, and that a cart is addressed by an unguessable key.

Reading it first is the difference between a storefront that works and one that charges the wrong total.

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

Input Schema

NameRequiredDescriptionDefault
modelNoYour model name or id (e.g. 'claude-opus-5'). Used to improve this documentation.
conversationIdNoAn existing conversation id. Omit to start a new one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and mostly does: it discloses that the return includes a required conversationId and reveals behavioral facts the API schema omits (no Authorization header, server-owned prices, unguessable cart keys). It does not mention response size, format, or whether the model parameter sends data externally, so it stops short of full disclosure.

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

Conciseness4/5

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

Front-loaded with the imperative and the key return value, and every clause carries substance about API pitfalls. It loses a point for the closing rhetorical flourish ("the difference between a storefront that works and one that charges the wrong total"), which is persuasion rather than instruction.

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?

There is no output schema, so the description must describe the return, and it does so with concrete detail about the conversationId and the embedded API guidance. It leaves open the response's shape/size and how the returned documentation should be consumed, which is a modest gap for a documentation-dump tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (model, conversationId) are already documented and the baseline applies. The description reinforces the conversationId's role as a prerequisite for other tools but adds no format or syntax detail beyond the schema.

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 action (call this first) and a concrete resource/payload: a conversationId plus the undocumented CloudCart Storefront API semantics (buyer scoping, checkoutUrl, formatted prices, cart key). An agent can tell this is the server's bootstrap/docs tool and not the schema-introspection or validation siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit ordering instruction: "Call this first, before anything else in this server." The reuse case is covered too, since the sibling schema notes that omitting conversationId starts a new conversation. No ambiguity about when to invoke it.

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

Deploy Server

Other Tools