mcp-rona
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 |
|---|---|
| rona_searchA | Search RONA (rona.ca) for products by keyword. Returns matching products with SKU, name, brand, model, rating, category, URL and image, plus the total result count, available filters (facets) and sort options. Use |
| rona_productA | Fetch the full product card for a RONA SKU (item number): name, brand, model, description, image, rating, barcode, category path, URL, and online availability. Note: RONA does not expose unit price or per-store stock through its public APIs, so price is null. |
| rona_store_availabilityA | Check whether a RONA SKU is available to buy online (inventory status). Note: real-time per-store stock levels and aisle/bay locations are not available from RONA's public APIs — this reports online purchasability only. Use rona_stores to find stores near a location. |
| rona_storesA | Find RONA stores nearest to a Canadian postal code (geocoded) or to latitude/longitude. Returns, per store: id, name, banner, address, city, province, postal code, phone, coordinates, distance (km), time zone, store URL and opening hours — sorted nearest first. |
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 has a clearly distinct purpose: fetching product details by SKU, searching by keyword, checking online availability, and finding nearby stores. No overlap in functionality.
All tool names follow a consistent 'rona_' prefix with snake_case descriptive nouns/verb+noun combinations (product, search, store_availability, stores). The pattern is uniform.
With 4 tools, the server covers the essential capabilities for a retail product information service: search, details, availability, and store locator. The count is well-scoped and each tool earns its place.
The tool set covers the main workflows: product discovery (search), detailed info (product), store locations, and online availability. Missing features like per-store stock or pricing are due to API limitations, not tool design gaps. Minor gap: no price or category browsing.