No customer input fields
Catalog readiness and key scope
Prove that OptiCat is reachable, classify access correctly, expose reference-data versions, and describe the configured key’s non-secret brand and VIN scope.
Follow the implementation from request to evidence.
Every node corresponds to a real resolver, operation, validation boundary, or response surface in the current code.
01 inputReadiness request- validated evidence
02 getAutoCareVersionVersion pulseReachability + reference versions
- accepted
03 getAutoCareBrandsLastUpdatedDatesBrand scopeFreshness and entitled count
- validated evidence
04 getAutoCareVehiclesByVINVIN scopeEnabled / denied / unknown
- validated evidence
05 gateAccess classifierSeparates entitlement from availability
- validated evidence
06 outputReadiness contractVersions, key_scope, evidence
The exact arguments the MCP server accepts.
This schema is generated from the registered Python tool. Required fields, defaults, nested models, and constraints are not maintained by hand.
interactionInteractionContext | nulloptional
nullWhat each upstream call needs—and earns.
Conditional calls are labeled. Validation describes the exact rule that allows evidence to advance to the next stage.
getAutoCareVersionEstablish catalog reachability and reference-data versions.- Requires
- X-Api-Key
- Produces
- PCdb/VCdb/PAdb versions · body status · latency
- Validation
- HTTP and JSON body status are classified independently; access failure is never an empty catalog.
getAutoCareBrandsLastUpdatedDatesBuild a non-secret brand-scope and freshness profile.- Requires
- accepted key
- Produces
- entitled brand count · freshness sample
- Validation
- An unrecognized or unavailable result is disclosed inside key_scope instead of failing the readiness result.
getAutoCareVehiclesByVINProbe VIN entitlement with a syntactically valid disposable VIN.- Requires
- accepted key · probe VIN
- Produces
- enabled · not_entitled · unknown
- Validation
- The decode result is discarded; only the entitlement class is returned.
Every important branch has a named outcome.
These are response decisions in the implemented service—not possible future behavior.
Return versions plus best-effort key-scope probes.
The primary readiness result survives and the probe’s limitation is explicit.
Never translated into a catalog-negative statement.
Return structured retryability and evidence.
One shared schema, highlighted for this tool.
Bright fields are populated by this path. Dimmed fields remain part of CatalogResponse but are not a normal output of this tool.
statusResultStatusrequired
summarystringrequired
reason_codeReasonCode | null
queryobject
metadataobject
completenessCompleteness
next_cursorstring | nulloptional
nullnext_pageinteger | nulloptional
nullpages_fetchedintegeroptional
0paging_modenone | page | cursor | capped | unknownoptional
"none"5 allowed valuesreturnedintegeroptional
0source_end_reachedbooleanoptional
This response reached the known end of the source query, even when earlier pages were returned separately.
falsetotalinteger | nulloptional
nulltruncatedbooleanoptional
falsevehiclesVehicleIdentity[]
partsPartRecord[]
relationshipsRelationshipRecord[]
relationship_outcomeRelationshipOutcome | null
fitmentFitmentDecision | null
interchange_validationsInterchangeValidation[]
clarificationClarification | null
pending_clarificationsClarification[]
Every open clarification dimension in one round (clarification stays = the first). Ask them together instead of one round trip per dimension.
warningsstring[]
errorCatalogError | null
evidenceEvidenceRecord[]
- No secret values are returned
- Access failure is not no-data
- Probe failures do not erase the primary result
get_catalog_statuspoc/opticat-mcp-v2/src/opticat_mcp_v2/server.pyOptiCatCatalogService.get_catalog_statuspoc/opticat-mcp-v2/src/opticat_mcp_v2/service.pyOptiCatClient.callpoc/opticat-mcp-v2/src/opticat_mcp_v2/client.pyWhat is known, and what could become possible.
Current gaps stay separate from product concepts so the visual never implies that an idea has already shipped.
- 01
Key scope is not yet surfaced in the operator console
- 02
There is no scheduled readiness history
- 03
Live paging ceilings are not described per operation
Trend latency, versions, and entitlement changes over deployments.
Alert when brand, VIN, or paging scope changes before customer answers regress.