FindMine Shopping Stylist
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Set to "development" for sample data | |
| FINDMINE_APP_ID | No | Your FindMine application ID | DEMO_APP_ID |
| FINDMINE_API_URL | No | FindMine API base URL | https://api.findmine.com |
| FINDMINE_API_VERSION | No | API version to use | v3 |
| FINDMINE_CACHE_TTL_MS | No | Cache time-to-live in ms (1 hour) | 3600000 |
| FINDMINE_CACHE_ENABLED | No | Enable response caching | true |
| FINDMINE_DEFAULT_REGION | No | Default region code | us |
| FINDMINE_DEFAULT_LANGUAGE | No | Default language code | en |
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_style_guideB | Get styling advice and tips for creating effective fashion recommendations |
| get_complete_the_lookC | Get outfit recommendations for a product |
| get_visually_similarC | Get visually similar products |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| outfit_completion | Get styling advice and complete outfit for a product |
| styling_guide | Get guidelines for providing effective fashion and styling advice |
| findmine_help | Learn how to use FindMine's tools and resources effectively |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have distinct purposes: get_complete_the_look focuses on outfit recommendations, get_style_guide provides styling advice and tips, and get_visually_similar finds visually similar products. While get_complete_the_look and get_visually_similar both involve product recommendations, their descriptions clarify that one is for outfits and the other for visual similarity, minimizing overlap. However, the boundary between get_complete_the_look and get_style_guide could be slightly ambiguous as both relate to fashion recommendations, but the descriptions help differentiate them.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, followed by descriptive phrases (complete_the_look, style_guide, visually_similar). This uniformity makes the tools predictable and easy to understand, with no deviations in naming conventions or styles.
With only 3 tools, the server feels thin for a shopping stylist domain, which might involve more operations like searching products, filtering by categories, or managing user preferences. While the tools cover key aspects (recommendations, advice, similarity), the limited count could restrict functionality and lead to gaps in handling complex styling tasks.
The tool surface is significantly incomplete for a shopping stylist. It lacks essential operations such as searching for products, retrieving product details, filtering by attributes (e.g., color, size), or handling user interactions (e.g., saving preferences, history). The existing tools focus only on recommendations and advice, leaving major gaps that could cause agent failures in real-world styling scenarios.