Contract surface
Tools and profiles
Six read-only MCP tools form the mandatory core retail read bundle. Four profiles group capabilities by purpose and dependency.
The six tools
| Tool | Question it answers | Access |
|---|---|---|
dealeragent.discovery.get_manifest | What does this gateway support? | Public allowed |
dealeragent.dealer.get | Who is the dealer or rooftop? | Dealer policy |
dealeragent.inventory.search | Which published vehicles match? | Dealer policy |
dealeragent.inventory.get_vehicle | What are the facts for this exact unit? | Dealer policy |
dealeragent.inventory.verify_availability | Is this vehicle authoritatively available now? | Rate-limited or authenticated |
dealeragent.pricing.get_disclosure | What price components and offer conditions apply? | Dealer policy |
The four profiles
The core bundle requires dealeragent.discovery/0.1, dealeragent.inventory.read/0.1, dealeragent.inventory.availability/0.1, and dealeragent.pricing.disclosure/0.1. A profile claim means every required tool, resource, schema, and behavior in that profile is implemented.
Read-only means no hidden action
All six tools declare read-only, non-destructive, idempotent intent. They create no lead, hold no vehicle, schedule no appointment, and make no legal or financial commitment.
Search is not verification. A vehicle returned by
NextPricing and offers→inventory.search was present in a discovery snapshot. Use verify_availability before making a current, authoritative claim.