Frisco 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_logsB | Returns persisted JSONL log events for the current or selected session. |
| tail_logsB | Returns the most recent events from persisted session logs. |
| loginA | Opens a visible Chromium browser to log in to Frisco manually. Run this first to establish a session. |
| finish_sessionA | Opens the browser at the checkout page so you can select a delivery time and pay. |
| clear_sessionB | Clears the saved session and closes the browser. |
| view_cartA | Returns the current contents and total of the Frisco cart. |
| add_items_to_cartA | Searches for and adds a list of products to the cart. By default appends to current cart, optionally clearing it first. |
| search_productsA | Searches frisco.pl for products and returns top matches with prices. |
| get_product_infoA | Gets detailed info for a product: nutritional values (macros per 100g), weight/grammage, ingredients, and price. |
| remove_item_from_cartA | Removes a specific product from the Frisco cart by name (partial match supported). |
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 10 tools
Most tools are clearly distinct: search_products vs get_product_info, add_items_to_cart vs view_cart vs remove_item_from_cart. The only real overlap is get_logs vs tail_logs, both returning persisted log events, though the descriptions (all events vs most recent) provide some separation.
Tool names consistently follow a verb_noun snake_case pattern: get_logs, tail_logs, finish_session, clear_session, add_items_to_cart, search_products, get_product_info, remove_item_from_cart, view_cart. Even 'login' fits the simple verb style without breaking the pattern.
10 tools is well-scoped for an online grocery automation server. Each tool maps to a clear workflow stage: session management, product discovery, cart manipulation, and checkout handoff. No redundant or superfluous tools.
The core shopping lifecycle is covered: login, search products, inspect product details, add/remove/view cart, and finish session for checkout. Minor gaps exist, such as no explicit quantity adjustment or standalone clear-cart tool, but add_items_to_cart's optional clearing and the manual checkout flow mitigate most dead ends.