AUTO411 Vehicle Intelligence

Resolve Vehicle Identity

resolve_vehicle

Read-only

Use this when identifying a vehicle from a full VIN or from year, make, and model with optional configuration refinements. Returns MATCHED_SINGLE, NEEDS_IDENTITY, or NO_MATCH and never silently chooses among legitimate configurations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_vehicle"
  }
}

Input Schema

Name	Required	Description
`vin`	No	Full 17-character VIN. Use VIN by itself as the identity path, or omit it and provide year, make, and model.
`make`	No	Vehicle make. Required with year and model when VIN is not provided.
`trim`	No	Optional identity refinement. Use only an explicitly known trim.
`year`	No	Model year. Required with make and model when VIN is not provided.
`model`	No	Customer-facing model family. Required with year and make when VIN is not provided.
`engine`	No	Optional identity refinement. Use only an explicitly known engine.
`drivetrain`	No	Optional identity refinement. Use only an explicitly known drivetrain.
`configuration_id`	No	AUTO411 configuration identifier returned by a prior NEEDS_IDENTITY response.

Output Schema

Name	Required	Description	Default
`error`	No
`choices`	No
`conflicts`	No
`fact_scope`	No
`choice_count`	No
`completeness`	No
`missing_fields`	No
`evidence_status`	No
`configuration_id`	No
`agent_instruction`	Yes
`canonical_vehicle`	No
`resolution_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 28, 2026

addedInput schema / properties / configuration_id / description

Added value: +"AUTO411 configuration identifier returned by a prior NEEDS_IDENTITY response."

addedInput schema / properties / drivetrain / description

Added value: +"Optional identity refinement. Use only an explicitly known drivetrain."

addedInput schema / properties / engine / description

Added value: +"Optional identity refinement. Use only an explicitly known engine."

addedInput schema / properties / make / description

Added value: +"Vehicle make. Required with year and model when VIN is not provided."

addedInput schema / properties / model / description

Added value: +"Customer-facing model family. Required with year and make when VIN is not provided."

addedInput schema / properties / trim / description

Added value: +"Optional identity refinement. Use only an explicitly known trim."

changedInput schema / properties / vin / description

Previous value: -"17-character VIN"New value: +"Full 17-character VIN. Use VIN by itself as the identity path, or omit it and provide year, make, and model."

addedInput schema / properties / year / description

Added value: +"Model year. Required with make and model when VIN is not provided."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "agent_instruction": {
+      "type": "string"
+    },
+    "canonical_vehicle": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "configuration_id": {
+              "type": "number"
+            },
+            "drivetrain": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "engine": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "generation": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "identity": {
+              "additionalProperties": {
+                "type": [
+                  "string",
+                  "number",
+                  "boolean",
+                  "null"
+                ]
+              },
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            },
+            "make": {
+              "type": "string"
+            },
+            "model": {
+              "type": "string"
+            },
+            "trim": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "year": {
+              "type": [
+                "number",
+                "string"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "choice_count": {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "choices": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "configuration_id": {
+            "type": "number"
+          },
+          "drivetrain": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "engine": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "evidence_status": {
+            "type": "string"
+          },
+          "generation": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "identity": {
+            "additionalProperties": {
+              "type": [
+                "string",
+                "number",
+                "boolean",
+                "null"
+              ]
+            },
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "trim": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "configuration_id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "completeness": {
+      "type": "string"
+    },
+    "configuration_id": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "conflicts": {
+      "items": {},
+      "type": "array"
+    },
+    "error": {
+      "additionalProperties": {},
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "code"
+      ],
+      "type": "object"
+    },
+    "evidence_status": {
+      "type": "string"
+    },
+    "fact_scope": {
+      "type": "string"
+    },
+    "missing_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "resolution_status": {
+      "enum": [
+        "INVALID_INPUT",
+        "MATCHED_SINGLE",
+        "NEEDS_IDENTITY",
+        "NO_MATCH",
+        "UNAVAILABLE",
+        "SOURCE_UNAVAILABLE"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "resolution_status",
+    "agent_instruction"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower; the description adds genuinely new behavior: the three outcome codes (MATCHED_SINGLE, NEEDS_IDENTITY, NO_MATCH) and the guarantee that it 'never silently chooses among legitimate configurations.' That disambiguation contract is exactly the kind of context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the usage trigger and followed by the outcome contract. No filler, no restatement of the title, and nothing an agent must skip over before acting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shapes need not be spelled out, yet the description still surfaces the three outcome states, which is the key decision input for the agent. Combined with 100% schema coverage and explicit conditional requirements on the parameters, only the multi-step NEEDS_IDENTITY resolution loop is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each parameter already documents its role and the VIN-vs-YMM conditional requirement, so the schema does the heavy lifting. The description adds no syntax, formatting, or refinement guidance (e.g. how trim/engine strings are matched) beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('identifying a vehicle') and enumerates the two identity paths (full VIN, or year/make/model with refinements). That is clearly distinct from the sibling retrieval tools (specs, safety, efficiency, fitment), but the description never names or contrasts a sibling explicitly, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this when identifying a vehicle...' gives a clear triggering condition and the acceptable input shapes. It also implies the follow-up flow via configuration_id ('returned by a prior NEEDS_IDENTITY response'), but it stops short of stating when NOT to use this tool or which sibling to pick instead for lookups like specs or fitment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AUTO411 Vehicle Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?