Reference Material
Non-normative examples: a conformant server manifest and a representative tool schema, to anchor the prose in concrete shapes.
7.1 Example server manifest
A conformant server advertises the specification version it implements, the domains it supports, and the conformance level per domain. This manifest is illustrative.
{
"automotive_mcp": {
"spec_version": "0.1",
"server": {
"name": "Example DMS MCP Adapter",
"vendor": "example-dms"
},
"domains": {
"inventory": { "level": 2 },
"leads": { "level": 3 },
"service": { "level": 2 },
"deals": { "level": 1 },
"signals": { "level": 1 },
"consent": { "level": 2 }
},
"auth": {
"type": "oauth2.1",
"scopes": [
"amcp:inventory:read",
"amcp:leads:read",
"amcp:leads:write",
"amcp:service:read",
"amcp:service:write",
"amcp:signals:read",
"amcp:consent:read",
"amcp:consent:write"
]
}
}
}7.2 Example tool schema
A representative tool definition. Inputs and outputs are JSON Schema; the error contract follows Core Concepts §3.4.
{
"name": "service.book_appointment",
"description": "Book a service appointment for a customer vehicle.",
"input_schema": {
"type": "object",
"required": ["vehicle_id", "start", "service_codes"],
"properties": {
"vehicle_id": { "type": "string" },
"start": { "type": "string", "format": "date-time" },
"service_codes": { "type": "array", "items": { "type": "string" } },
"advisor_id": { "type": "string" }
}
},
"output_schema": {
"type": "object",
"required": ["appointment_id", "status"],
"properties": {
"appointment_id": { "type": "string" },
"status": { "type": "string", "enum": ["booked", "waitlisted"] },
"start": { "type": "string", "format": "date-time" }
}
}
}7.3 Example resource
{
"id": "veh_8Kd02p",
"type": "vehicle",
"vin": "1HGCM82633A004352",
"condition": "used",
"year": 2021,
"make": "Toyota",
"model": "RAV4",
"trim": "XLE",
"mileage": { "value": 38120, "unit": "mi" },
"price": { "amount": 2899900, "currency": "USD" },
"status": "available"
}7.4 Reference implementation
A reference server and a conformance test suite are planned to accompany ratification, so that "conformant" is something a vendor can prove, not just claim. Releases are announced on the Updates page as the council publishes them.