Shoplazza MCP Tool
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-lessjsD | – |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool stands alone with no other tools to confuse it with.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The naming pattern cannot be inconsistent when only one exists.
One tool is too few for a server named 'Shoplazza MCP Tool', which suggests an e-commerce or store management domain. A single tool cannot provide meaningful coverage for such a broad purpose, making it severely under-scoped.
The server is severely incomplete for its implied e-commerce domain. With only a 'get-lessjs' tool (which lacks a description but seems unrelated to core store operations), there are no tools for managing products, orders, customers, or other essential store functions, leaving major gaps.