Sklarstad Storefront MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsA | List every Sklarstad LLC product. Returns each product's slug, display name, publisher, one-line summary, and availability (live, or pre-launch with a launch date) — enough to decide which (if any) is relevant before calling get_product for full details. |
| get_productA | Get full details for one product: summary, track record, what kinds of work it's built for, requirements, footage/data privacy, how it's updated, where to send feedback, availability, and every pricing tier with its description (and checkout URL once on sale). Args: slug: A product slug from list_products, e.g. "film-shoot". |
| get_checkout_urlA | Get the checkout URL for one pricing tier of one product. Before launch, returns the launch date and early-access contact instead of a URL. Args: slug: A product slug from list_products, e.g. "film-shoot". tier_name: A tier name from that product's pricing_tiers, e.g. "Per-shoot". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, non-overlapping purpose: list_products provides an overview, get_product gives full details for a single product, and get_checkout_url retrieves the purchase link for a specific tier. An agent can easily distinguish which tool to call based on the information needed.
All tool names follow a consistent verb_noun pattern (list_products, get_product, get_checkout_url). The naming is predictable and aligns with standard conventions, making it easy to infer functionality.
Three tools is well-scoped for a storefront MCP. Each tool serves a distinct, necessary function (browse, inspect, purchase) without redundancy or bloat. The count feels appropriate for the domain.
The tool surface covers the complete customer-facing lifecycle: listing products, retrieving full details, and obtaining checkout URLs. There are no obvious gaps for the stated purpose, and the inclusion of pricing tiers and availability in get_product avoids dead ends.