Arham Jewellers MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_BASE_URL | Yes | Base URL of the Arham Jewellers backend API |
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_product_detailsA | Get detailed information about a specific product by its ID. Use this after search_products to get full details of a product. |
| get_product_by_barcodeA | Find a product by its barcode number. Useful when a customer scans or reads a barcode. |
| get_categoriesA | Browse categories step by step. Call with no params to see Karat options (Level 1). Pass a parent_id to see its children (Level 2=Collection or Level 3=Style). Only Level 3 IDs work with get_category_products. Ask the user what they are looking for (karat, collection, style) before drilling down. |
| get_category_productsA | Get products in a category. IMPORTANT: category_id MUST be a Level 3 (Style) ID. Use get_categories with parent_id to drill down to Level 3 first. Level 1 and Level 2 IDs will return 0 products. |
| get_current_gold_rateA | Get the current gold rate per gram. Returns the latest rate set by the store. |
| get_gold_rate_historyB | Get historical gold rates. Returns a list of past rate entries. |
| get_user_ordersB | Get order history for a user. Returns a paginated list of orders with their items and status. |
| get_order_detailsA | Get details of a specific order from the user's order history. Returns full order info including all items. |
| place_orderA | Place an order for one or more products. IMPORTANT: Ask the user to confirm before placing an order. This action will create a real order in the system. |
| get_store_infoC | Get store information like contact details, about us, terms, refund policy, etc. |
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
Each tool has a clearly distinct purpose: browsing categories, retrieving products in a category, gold rates, orders, barcode lookup, product details, store info, user orders, and placing orders. No overlap between tools.
All tools follow a consistent verb_noun pattern with underscore separators (e.g., get_categories, place_order). No mixing of conventions.
10 tools are well-scoped for a jewelry store MCP server, covering browsing, ordering, and store information without being overly numerous or too few.
The tool set covers core operations (browse, get details, order), but notably lacks a search tool despite get_product_details referencing search_products. Missing update/delete for orders and customer support tools, leaving moderate gaps.