JOY Automart MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOY_AGENT_TOKEN | No | Optional buyer-issued agent token (joyagt_...) for authenticated tools such as quote_order, place_order, create_rfq, get_order_status, and list_my_orders. Public tools work without it. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_partsA | Find spare-part candidates in JOY's Bangladesh catalogue; use search_vehicles for whole cars.
|
| get_partA | Read one spare part's public price, availability and fitment restrictions; search_parts supplies its ID.
|
| search_vehiclesA | Discover cars for sale in JOY Auto Exchange; use get_vehicle for detail, compare_vehicles for a shortlist or search_auctions for auction links.
|
| get_vehicleA | Read a car listing's public specifications, asking price and inspection evidence; search_vehicles discovers candidates and compare_vehicles compares them.
|
| get_auctionA | Observe one car auction's public bid state; search_auctions discovers IDs and get_vehicle supplies the linked car's facts.
|
| search_auctionsA | Discover existing public car-auction IDs for get_auction; use get_vehicle for a known listing's details.
|
| compare_vehiclesA | Compare a selected car shortlist; use search_vehicles to discover candidates or get_vehicle for one car.
|
| get_buying_guideA | Read published Bangladesh retail-parts payment, delivery and human-contact terms before explaining a purchase.
|
| prepare_vehicle_handoffA | Prepare a listing link and pre-filled WhatsApp enquiry for a human considering one car; use prepare_part_handoff for spare parts and compare_vehicles before choosing between cars. Choose vehicle_id from a shortlisted listing, not an auction ID. A slug is resolved to the canonical listing_id before the message is composed. note records the buyer's request; it cannot change the asking price, certify condition or authorize a bid. The link embeds the note, so omit unnecessary personal details. Anonymous fresh lookup. This is the endpoint of the public research workflow: the human decides whether to open and send the enquiry, then JOY confirms availability, inspection and terms. No seller contact, booking, reservation, bid, order or payment is performed. |
| prepare_part_handoffA | Prepare product and pre-filled WhatsApp links for a human parts enquiry; use prepare_vehicle_handoff for whole cars.
|
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 targets a distinct resource+action: search/get pairs for parts, vehicles and auctions, plus compare_vehicles, get_buying_guide and the two prepare_*_handoff tools. The only mild overlap is search_vehicles vs search_auctions (auctions scan vehicle listings), but the descriptions explicitly redirect between them so an agent can distinguish them.
All ten tools follow a consistent snake_case verb_noun pattern (search_*, get_*, compare_vehicles, prepare_*_handoff). The singular/plural distinction (search_parts vs get_part, search_vehicles vs get_vehicle) is a sensible and consistent convention rather than an inconsistency.
Ten tools is well-scoped for a marketplace covering three resource families (parts, vehicles, auctions) plus comparison, terms, and handoffs. Every tool earns its place with no redundancy or filler.
The surface covers the full public research workflow for each domain: discovery, detail, comparison, auction status, terms, and human handoff endpoints for both parts and vehicles. Read-only/anonymous scope is intentional and explicitly noted, with no dead ends within that stated purpose.