liquidus-005
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_productsC | browse: list products from the storefront catalog |
| get_productC | browse: retrieve a product by id |
| list_taxonomiesC | browse: list taxonomies |
| get_orderB | post-order: retrieve an order by number (with order-token for guest checkout) |
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 4 tools
Each tool targets a distinct resource (order, product, products, taxonomies) with no overlap. The operations are clearly differentiated: single retrieval vs. listing.
All tools follow a consistent verb_noun pattern: get_ for single entities and list_ for collections. The naming is predictable and uniform.
With 4 tools, the server is minimally scoped. While it could be sufficient for a read-only browsing service, it feels thin for a typical e-commerce server and may leave agents wanting more functionality.
The server covers only retrieval operations for products, orders, and taxonomies. Missing common actions like listing orders, creating or updating products, or managing carts, which are significant gaps for a storefront API.