OpenDealer MCP Server

Get Deal Score

get_deal_score

Read-onlyIdempotent

Deal score and market context for one listing: a 1 to 100 score with a rating, price versus the market average, days on lot, price history, and similar vehicles in the market.

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": "get_deal_score"
  }
}

Input Schema

Name	Required	Description
`vin`	No	17-character Vehicle Identification Number
`dealerId`	No	Score this dealer when the VIN is listed at more than one rooftop. Same as GET /v1/vehicles/:vin/insights dealerId.
`vertical`	No	Shopper vertical. An absent value covers every public vertical (cars and off-road). Live verticals come from list_verticals.
`listingId`	No	Canonical listing id (`dealerId-or-slug:VIN`). Scores that rooftop when the VIN is listed at more than one store.
`dealerSlug`	No	Score this rooftop slug when the VIN is listed at more than one store. Same as insights dealerSlug.

Output Schema

Name	Required	Description	Default
`vin`	No
`dealScore`	No
`priceHistory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / vertical / description

Previous value: -"Shopper vertical. Omit for every public vertical (cars and off-road). Live verticals come from list_verticals."New value: +"Shopper vertical. An absent value covers every public vertical (cars and off-road). Live verticals come from list_verticals."

Changed8 schema fields changedNov 11, 2026
- addedInput schema / $schema
```
Added value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / vin / pattern
```
Added value: +"^[A-HJ-NPR-Z0-9]{17}$"
```
- addedInput schema / properties / vin / type
```
Added value: +"string"
```
- addedOutput schema / $schema
```
Added value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
- changedOutput schema / properties / dealScore / additionalProperties
```
Previous value: -trueNew value: +{}
```
- changedOutput schema / properties / priceHistory / items / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / vertical / description

Previous value: -"Shopper vertical. Omit for every public vertical (cars today). Live verticals come from list_verticals."New value: +"Shopper vertical. Omit for every public vertical (cars and off-road). Live verticals come from list_verticals."

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / vertical

Added value: +{
+  "description": "Shopper vertical. Omit for every public vertical (cars today). Live verticals come from list_verticals.",
+  "minLength": 1,
+  "type": "string"
+}

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / dealerId

Added value: +{
+  "description": "Score this dealer when the VIN is listed at more than one rooftop. Same as GET /v1/vehicles/:vin/insights dealerId.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

addedInput schema / properties / dealerSlug

Added value: +{
+  "description": "Score this rooftop slug when the VIN is listed at more than one store. Same as insights dealerSlug.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

Changed1 schema field changedOct 17, 2026
- removedInput schema / required
```
Removed value: -[
-  "vin"
-]
```

Changed3 schema fields changedOct 17, 2026

addedInput schema / properties / listingId

Added value: +{
+  "description": "Canonical listing id (`dealerId-or-slug:VIN`). Scores that rooftop when the VIN is listed at more than one store.",
+  "maxLength": 300,
+  "minLength": 19,
+  "type": "string"
+}

removedInput schema / properties / vin / pattern
```
Removed value: -"^[A-HJ-NPR-Z0-9]{17}$"
```
removedInput schema / properties / vin / type
```
Removed value: -"string"
```

Changed8 schema fields changedJul 30, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- changedOutput schema / properties / dealScore / additionalProperties
```
Previous value: -{}New value: +true
```
- addedOutput schema / properties / dealScore / properties
```
Added value: +{}
```
- removedOutput schema / properties / priceHistory / items / $ref
```
Removed value: -"#/properties/dealScore"
```
- addedOutput schema / properties / priceHistory / items / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / priceHistory / items / properties
```
Added value: +{}
```
- addedOutput schema / properties / priceHistory / items / type
```
Added value: +"object"
```
First observedJul 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds that results include derived analytics (score, rating, days on lot, price history, comparable vehicles), which is modest added context, but says nothing about freshness/latency of the score, whether a missing VIN returns an error or empty result, or rate limits.

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

Conciseness4/5

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

A single front-loaded sentence naming the resource first, then the returned fields. Efficient with no filler; the only cost is that the enumerated field list duplicates what the output schema already declares.

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?

With a full output schema and rich annotations, the definition only needs to convey scope and payload, which it does. The residual gap is that with zero required parameters the description never explains the minimal valid invocation, though the schema's per-parameter notes partially cover this.

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%, including the rooftop-disambiguation semantics for dealerId, listingId and dealerSlug, so the schema carries the parameter burden. The description adds nothing about how to choose among the five identifier parameters or which combination is required when none are marked required, leaving that entirely to the schema.

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?

States a specific resource and scope: deal score plus market context for a single listing, enumerating the payload (1-100 score, rating, price vs market average, days on lot, price history, similar vehicles). It does not name or distinguish itself from near-neighbors such as compare_market or get_similar_vehicles, so an agent must infer the boundary, but the verb+resource is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance appears in the description. The implicit 'one listing' framing is the only scoping signal; nothing tells the agent how this differs from compare_market or get_vehicle_rankings, or what the caller needs before invoking it.

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

All OpenDealer MCP Server 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?