Free US VIN decoding and research; VIN-optional market appraisals via a separate pilot endpoint.
Scored across 4 tools
The four tools target fairly distinct functions: two static-info tools (about, pricing_and_tiers), one document search/retrieval tool (research_library), and one VIN decoder. The main overlap is between tradebasis_about and tradebasis_pricing_and_tiers, both of which serve static informational markdown, but their content boundaries are reasonably clear.
All tools share a consistent tradebasis_ prefix, which aids grouping. However, three are noun-phrases (about, pricing_and_tiers, research_library) while one is verb_noun (vin_decode), so the action pattern is not uniform, though still readable.
Four tools is on the thin side for a server branded as an automotive appraisal product, with two of them being static informational content rather than functional operations. The count is not extreme but feels under-scoped for the apparent domain.
Despite the 'Appraisal' name, no tool performs valuation, comparable-listing lookup, or market-data retrieval, and vin_decode explicitly returns none of these. Core lifecycle operations implied by the server's purpose are missing, leaving agents unable to complete the primary appraisal workflow.
What TradeBasis is, the problem it solves, what makes it different, and who it's for, plus how to connect to the separate free, limited US appraisal pilot. Static markdown; as_of is the explicit content review date.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds genuinely useful context beyond that: it is static markdown and as_of is an explicit content-review date, which tells the agent the content may be stale and is not live data. It does not describe output format or size, keeping it from a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads the core content scope and appends the static/freshness caveat. Dense but every clause carries information; the only minor cost is a long comma-separated enumeration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only informational tool with no output schema, the description supplies enough: content coverage, static nature, and the as_of freshness signal. It is not fully exhaustive (no sense of length or structure of the markdown), but nothing needed to invoke it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the schema-baseline is 4. The mention of 'as_of' refers to the returned payload rather than an input, which is mildly ambiguous but harmless given there are no parameters to document.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly enumerates the content the tool returns (what TradeBasis is, the problem it solves, differentiators, target audience, and how to reach the appraisal pilot), which is a specific and verifiable scope for an 'about' resource. It does not name or distinguish itself from the sibling tools (pricing_and_tiers, research_library, vin_decode), so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: an agent can infer this is the orientation/overview tool, but there is no explicit statement of when to call it versus tradebasis_pricing_and_tiers or tradebasis_research_library, nor any exclusion criteria. Adequate but leaves the routing decision to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TradeBasis paid subscription tiers — Lite (1 user, $99/mo USD) vs Pro (up to 10 users, $249/mo USD). Separate from the free MCP appraisal pilot and the $99 one-time consumer report. Static markdown; as_of is the explicit content review date.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely new context beyond that: the content is static markdown and carries an explicit as_of review date, which tells the agent the answer is fixed and how stale it may be. Minor risk that naming 'as_of' reads like an input despite there being zero parameters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with the pricing facts front-loaded, followed by scope exclusions and a freshness note. Every clause carries information; only the dangling 'as_of' reference could be trimmed or clarified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only lookup with no output schema, the description covers what the tool returns (tier names, seat counts, prices) and adds a freshness caveat. The only gap is not describing the shape of the returned markdown, which is a small omission.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so the baseline is 4 and the schema has nothing to describe. The passing mention of as_of as a content field is mildly useful but is not an input, so it neither helps nor hurts parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource — TradeBasis paid subscription tiers — with concrete contents (Lite 1 user $99/mo, Pro 10 users $249/mo). It clearly delimits itself from the free MCP appraisal pilot and the one-time consumer report, so an agent knows this is the paid-plan pricing page. It does not explicitly contrast itself with the actual sibling tools (about, research_library, vin_decode), which keeps it short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: reach for this when a user asks about paid plan pricing or tier limits. The exclusion note about the free pilot and the consumer report helps disambiguate adjacent offerings, but there is no explicit 'use this when / not when' statement relative to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search published TradeBasis US dealer research, BHPH (buy here pay here) economics and portfolio benchmarks, the experimental BHPH Macro Conditions Index and its methodology, public blog articles, and legacy briefs. No arguments lists the catalog. topic retrieves a document by ID/slug/title; topic + section retrieves a section or continuation part. query searches; optional limit is an integer 1–20 (default 5). These modes cannot be combined. Returns published Markdown tables, dated evidence, sources and qualifications, not new financial analysis. Long documents return an overview and section directory. Publication is rechecked on every retrieval; unverifiable sources return retryable errors, not cached article text. Blog access uses the public internet. Publication/update dates, CMS modification, data coverage and retrieval time are distinct. Structured output uses operation=list/search/get/section/invalid; retrieval includes the requested Markdown and publisher caveats. Unknown dates and coverage remain null. No search cursor is supported; use returned section/part IDs for long content.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Search results only: integer 1–20, default 5. Requires query. | |
| query | No | Ordinary-language search of published dealer research and blog articles. Cannot be combined with topic or section. | |
| topic | No | Stable document ID, legacy slug, or title. Alone retrieves a document; with section retrieves that section. Empty topic retains legacy listing behavior. | |
| section | No | Section or versioned part ID returned by this tool. Requires topic. Oversized sections list all continuation IDs. |
| Name | Required | Description |
|---|---|---|
| code | No | |
| topic | No | |
| reason | No | |
| status | No | |
| caveats | Yes | |
| content | No | Requested Markdown, including source qualifications. May be an explicitly labeled overview or section-part directory. |
| message | No | |
| outcome | Yes | |
| results | No | |
| complete | No | |
| document | No | |
| sections | No | |
| documents | No | |
| operation | Yes | |
| retryable | Yes | |
| part_index | No | |
| section_id | No | |
| suggestions | No | |
| next_section | No | |
| result_count | No | |
| retrieved_at | Yes | |
| full_document | No | |
| part_complete | No | |
| schema_version | Yes | |
| source_caveats | No | Publisher qualifications when present; null does not assert that the source has no limitations. |
| available_slugs | No | |
| synchronization | Yes | |
| section_complete | No | |
| continuation_sections | No | |
| eligibility_verified_at | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnly/openWorld/non-destructive, and the description adds substantial context beyond them: publication is rechecked on every retrieval, unverifiable sources return retryable errors rather than cached text, blog access uses the public internet, long documents return an overview plus section directory, and date/coverage/retrieval-time fields are distinct with unknowns left null. This is rich behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose and mode routing are front-loaded and every sentence carries operational information, but the prose is dense and choppy, and a few clauses (limit range, default 5) duplicate the schema. Slightly long, though not padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, yet the description still explains the structured output enum (list/search/get/section/invalid), publisher caveats, and null handling. Combined with the mode rules and error behavior, an agent has everything needed to invoke this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is already 100%, so the baseline is 3, but the description adds relational semantics the schema cannot express: that the modes cannot be combined and how topic/section/query/limit interact. It restates limit as 1–20 default 5, which the schema already carries, so it stops short of a 5.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening sentence names the specific verb (search) and enumerates the exact resource set: US dealer research, BHPH economics/benchmarks, the Macro Conditions Index, blog articles, and legacy briefs. It also spells out the four access modes (catalog, get, section, search) so the agent can distinguish this from siblings like tradebasis_about or tradebasis_pricing_and_tiers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit when-to-use guidance for every mode: no arguments lists the catalog, topic retrieves by ID/slug/title, topic+section retrieves a section or continuation, query searches, and 'these modes cannot be combined.' It also states the alternative for long content (use returned section/part IDs, no search cursor). Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Decode a 17-character VIN into vehicle identity: year, make, model, trim, body style, drivetrain, engine, transmission and fuel type. Hybrid, plug-in hybrid and battery-electric vehicles also return their electrification level and, where stated, battery and charging facts. Identification only — this tool returns no valuation, no comparable listings and no market data.
| Name | Required | Description | Default |
|---|---|---|---|
| vin | Yes | Required. The vehicle's 17-character VIN. Lowercase and whitespace are normalized; I, O and Q are rejected, never guessed. Ask the user if missing. Identification only, not valuation. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: lowercase/whitespace normalization, hard rejection of I/O/Q characters, and the fact that hybrid/EV VINs return electrification level plus battery and charging facts.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the action and output fields, then the EV-specific behavior, then the scope exclusion. Every sentence carries information and none is redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description compensates by enumerating what fields are returned, including EV-specific returns. With the sole parameter fully documented in the schema and safety covered by annotations, an agent has enough to invoke correctly; only explicit error/failure behavior is left unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema itself already documents normalization, character rejection, the 'ask the user if missing' guidance, and the identification-only scope. The description adds no additional syntax or format detail beyond what the schema provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Decode a 17-character VIN') and enumerates the returned identity fields (year, make, model, trim, engine, etc.), so an agent knows exactly what it produces. It also delineates the boundary against valuation/market data, making it clearly distinct from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a clear scope exclusion: 'Identification only — this tool returns no valuation, no comparable listings and no market data,' which tells the agent what this tool is not for. It does not name an alternative tool to use instead, but the siblings are non-competing (about, pricing, research library), so no explicit routing is strictly needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
tradebasis_research_library1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "allOf": [
+ {
+ "else": {
+ "allOf": [
+ {
+ "if": {
+ "properties": {
+ "operation": {
+ "const": "list"
+ }
+ }
+ },
+ "then": {
+ "required": [
+ "documents",
+ "complete"
+ ]
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "operation": {
+ "const": "search"
+ }
+ }
+ },
+ "then": {
+ "required": [
+ "results",
+ "result_count",
+ "complete"
+ ]
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "operation": {
+ "const": "get"
+ }
+ }
+ },
+ "then": {
+ "required": [
+ "document",
+ "content",
+ "sections",
+ "full_document",
+ "section_complete",
+ "eligibility_verified_at",
+ "source_caveats"
+ ]
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "operation": {
+ "const": "section"
+ }
+ }
+ },
+ "then": {
+ "required": [
+ "document",
+ "content",
+ "sections",
+ "full_document",
+ "section_complete",
+ "eligibility_verified_at",
+ "source_caveats",
+ "section_id",
+ "continuation_sections",
+ "part_complete",
+ "part_index",
+ "next_section"
+ ]
+ }
+ }
+ ],
+ "properties": {
+ "code": false,
+ "operation": {
+ "enum": [
+ "list",
+ "search",
+ "get",
+ "section"
+ ]
+ },
+ "status": false
+ }
+ },
+ "if": {
+ "properties": {
+ "outcome": {
+ "enum": [
+ "RESEARCH_INVALID_INPUT",
+ "RESEARCH_BRIEF_NOT_FOUND",
+ "RESEARCH_SECTION_NOT_FOUND",
+ "RESEARCH_SECTION_VERSION_CHANGED",
+ "RESEARCH_TEMPORARILY_UNAVAILABLE"
+ ]
+ }
+ }
+ },
+ "then": {
+ "properties": {
+ "content": false,
+ "document": false,
+ "documents": false,
+ "results": false
+ },
+ "required": [
+ "status",
+ "code",
+ "message"
+ ]
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "outcome": {
+ "const": "RESEARCH_INVALID_INPUT"
+ }
+ }
+ },
+ "then": {
+ "properties": {
+ "code": {
+ "const": "RESEARCH_INVALID_INPUT"
+ }
+ }
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "outcome": {
+ "const": "RESEARCH_BRIEF_NOT_FOUND"
+ }
+ }
+ },
+ "then": {
+ "properties": {
+ "code": {
+ "const": "RESEARCH_BRIEF_NOT_FOUND"
+ }
+ }
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "outcome": {
+ "const": "RESEARCH_SECTION_NOT_FOUND"
+ }
+ }
+ },
+ "then": {
+ "properties": {
+ "code": {
+ "const": "RESEARCH_SECTION_NOT_FOUND"
+ }
+ }
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "outcome": {
+ "const": "RESEARCH_SECTION_VERSION_CHANGED"
+ }
+ }
+ },
+ "then": {
+ "properties": {
+ "code": {
+ "const": "RESEARCH_SECTION_VERSION_CHANGED"
+ }
+ }
+ }
+ },
+ {
+ "if": {
+ "properties": {
+ "outcome": {
+ "const": "RESEARCH_TEMPORARILY_UNAVAILABLE"
+ }
+ }
+ },
+ "then": {
+ "properties": {
+ "code": {
+ "const": "RESEARCH_TEMPORARILY_UNAVAILABLE"
+ }
+ }
+ }
+ }
+ ],
+ "properties": {
+ "available_slugs": {
+ "items": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "type": "array"
+ },
+ "caveats": {
+ "items": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "type": "array"
+ },
+ "code": {
+ "enum": [
+ "RESEARCH_INVALID_INPUT",
+ "RESEARCH_BRIEF_NOT_FOUND",
+ "RESEARCH_SECTION_NOT_FOUND",
+ "RESEARCH_SECTION_VERSION_CHANGED",
+ "RESEARCH_TEMPORARILY_UNAVAILABLE"
+ ],
+ "type": "string"
+ },
+ "complete": {
+ "type": "boolean"
+ },
+ "content": {
+ "description": "Requested Markdown, including source qualifications. May be an explicitly labeled overview or section-part directory.",
+ "minLength": 1,
+ "type": "string"
+ },
+ "continuation_sections": {
+ "items": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "type": "array"
+ },
+ "document": {
+ "$ref": "#/properties/documents/items"
+ },
+ "documents": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "canonical_url": {
+ "anyOf": [
+ {
+ "format": "uri",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "cms_modified_at": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "content_version": {
+ "minLength": 1,
+ "pattern": "^[a-f0-9]{64}$",
+ "type": "string"
+ },
+ "data_coverage": {
+ "anyOf": [
+ {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Source-supported observation period, not the publication or retrieval date."
+ },
+ "description": {
+ "type": "string"
+ },
+ "id": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "last_substantive_update": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "legacy_as_of": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "publication_date": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "publisher_version": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "slug": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "source": {
+ "enum": [
+ "website",
+ "wordpress",
+ "legacy"
+ ],
+ "type": "string"
+ },
+ "title": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "type": {
+ "enum": [
+ "research",
+ "index",
+ "blog"
+ ],
+ "type": "string"
+ },
+ "update_basis": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "webpage_modified_at": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "webpage_published_at": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ }
+ },
+ "required": [
+ "id",
+ "slug",
+ "title",
+ "description",
+ "type",
+ "canonical_url",
+ "publication_date",
+ "last_substantive_update",
+ "update_basis",
+ "data_coverage",
+ "publisher_version",
+ "cms_modified_at",
+ "webpage_published_at",
+ "webpage_modified_at",
+ "legacy_as_of",
+ "content_version",
+ "source"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "eligibility_verified_at": {
+ "$ref": "#/properties/retrieved_at"
+ },
+ "full_document": {
+ "type": "boolean"
+ },
+ "message": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "next_section": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "operation": {
+ "enum": [
+ "list",
+ "search",
+ "get",
+ "section",
+ "invalid"
+ ],
+ "type": "string"
+ },
+ "outcome": {
+ "enum": [
+ "OK",
+ "PARTIAL_RESULTS",
+ "NO_RESULTS",
+ "RESEARCH_INVALID_INPUT",
+ "RESEARCH_BRIEF_NOT_FOUND",
+ "RESEARCH_SECTION_NOT_FOUND",
+ "RESEARCH_SECTION_VERSION_CHANGED",
+ "RESEARCH_TEMPORARILY_UNAVAILABLE"
+ ],
+ "type": "string"
+ },
+ "part_complete": {
+ "type": "boolean"
+ },
+ "part_index": {
+ "anyOf": [
+ {
+ "exclusiveMinimum": 0,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "reason": {
+ "enum": [
+ "SOURCE_UNAVAILABLE",
+ "SOURCE_LIMIT",
+ "SOURCE_INVALID",
+ "SOURCE_BUSY"
+ ],
+ "type": "string"
+ },
+ "result_count": {
+ "maximum": 20,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "results": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "canonical_url": {
+ "$ref": "#/properties/documents/items/properties/canonical_url"
+ },
+ "cms_modified_at": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "content_version": {
+ "$ref": "#/properties/documents/items/properties/content_version"
+ },
+ "data_coverage": {
+ "$ref": "#/properties/documents/items/properties/data_coverage"
+ },
+ "description": {
+ "$ref": "#/properties/documents/items/properties/description"
+ },
+ "excerpt": {
+ "type": "string"
+ },
+ "id": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "last_substantive_update": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "legacy_as_of": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "publication_date": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "publisher_version": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "section_ids": {
+ "items": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "type": "array"
+ },
+ "slug": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "source": {
+ "$ref": "#/properties/documents/items/properties/source"
+ },
+ "title": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "type": {
+ "$ref": "#/properties/documents/items/properties/type"
+ },
+ "update_basis": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "webpage_modified_at": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "webpage_published_at": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ }
+ },
+ "required": [
+ "id",
+ "slug",
+ "title",
+ "description",
+ "type",
+ "canonical_url",
+ "publication_date",
+ "last_substantive_update",
+ "update_basis",
+ "data_coverage",
+ "publisher_version",
+ "cms_modified_at",
+ "webpage_published_at",
+ "webpage_modified_at",
+ "legacy_as_of",
+ "content_version",
+ "source",
+ "excerpt",
+ "section_ids"
+ ],
+ "type": "object"
+ },
+ "maxItems": 20,
+ "type": "array"
+ },
+ "retrieved_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "retryable": {
+ "type": "boolean"
+ },
+ "schema_version": {
+ "const": "1.0",
+ "type": "string"
+ },
+ "section_complete": {
+ "type": "boolean"
+ },
+ "section_id": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "sections": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "canonical_url": {
+ "anyOf": [
+ {
+ "format": "uri",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "title": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "canonical_url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "source_caveats": {
+ "description": "Publisher qualifications when present; null does not assert that the source has no limitations.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "const": "error",
+ "type": "string"
+ },
+ "suggestions": {
+ "items": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ },
+ "type": "array"
+ },
+ "synchronization": {
+ "additionalProperties": false,
+ "properties": {
+ "publication_hook": {
+ "const": "local-filesystem",
+ "type": "string"
+ },
+ "refresh_interval_seconds": {
+ "const": 240,
+ "type": "number"
+ },
+ "sources": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "content_version": {
+ "anyOf": [
+ {
+ "minLength": 1,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "document_count": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "error_code": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version"
+ },
+ "last_attempt_at": {
+ "anyOf": [
+ {
+ "$ref": "#/properties/retrieved_at"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "last_successful_refresh": {
+ "anyOf": [
+ {
+ "$ref": "#/properties/retrieved_at"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "last_verified_at": {
+ "anyOf": [
+ {
+ "$ref": "#/properties/retrieved_at"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "next_refresh_due": {
+ "anyOf": [
+ {
+ "$ref": "#/properties/retrieved_at"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "source": {
+ "enum": [
+ "website",
+ "wordpress",
+ "legacy"
+ ],
+ "type": "string"
+ },
+ "status": {
+ "enum": [
+ "cold",
+ "refreshing",
+ "ready",
+ "unavailable"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "source",
+ "status",
+ "last_attempt_at",
+ "last_successful_refresh",
+ "last_verified_at",
+ "next_refresh_due",
+ "document_count",
+ "content_version",
+ "error_code"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "wordpress_publication_hook": {
+ "const": "not_connected",
+ "type": "string"
+ }
+ },
+ "required": [
+ "sources",
+ "refresh_interval_seconds",
+ "publication_hook",
+ "wordpress_publication_hook"
+ ],
+ "type": "object"
+ },
+ "topic": {
+ "$ref": "#/properties/synchronization/properties/sources/items/properties/content_version/anyOf/0"
+ }
+ },
+ "required": [
+ "schema_version",
+ "operation",
+ "outcome",
+ "retrieved_at",
+ "synchronization",
+ "caveats",
+ "retryable"
+ ],
+ "type": "object"
+}tradebasis_vin_decode2 fields changedInput schema / properties / vin / descriptionPrevious value: -"Required. The 17-character Vehicle Identification Number to decode."New value: +"Required. The vehicle's 17-character VIN. Lowercase and whitespace are normalized; I, O and Q are rejected, never guessed. Ask the user if missing. Identification only, not valuation."Input schema / requiredAdded value: +[
+ "vin"
+]tradebasis_research_library5 fields changedInput schema / properties / limitAdded value: +{
+ "description": "Search results only: integer 1–20, default 5. Requires query.",
+ "maximum": 20,
+ "minimum": 1,
+ "type": "integer"
+}Input schema / properties / queryAdded value: +{
+ "description": "Ordinary-language search of published dealer research and blog articles. Cannot be combined with topic or section.",
+ "maxLength": 500,
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / sectionAdded value: +{
+ "description": "Section or versioned part ID returned by this tool. Requires topic. Oversized sections list all continuation IDs.",
+ "maxLength": 256,
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / topic / descriptionPrevious value: -"Optional brief slug or title. Omit to list all available briefs."New value: +"Stable document ID, legacy slug, or title. Alone retrieves a document; with section retrieves that section. Empty topic retains legacy listing behavior."Input schema / properties / topic / maxLengthAdded value: +256tradebasis_vin_decode2 fields changedInput schema / properties / vin / descriptionPrevious value: -"The 17-character Vehicle Identification Number to decode."New value: +"Required. The 17-character Vehicle Identification Number to decode."Input schema / requiredRemoved value: -[
- "vin"
-]tradebasis_vin_decodetradebasis_abouttradebasis_pricing_and_tierstradebasis_research_libraryDecode US-market VINs and list NHTSA recall campaigns for the make, model and year. Free, no auth.
Vehicle data for AI: VIN decoder, automotive specs, stolen checks, valuation and way more.
Decodes US VINs and looks up open NHTSA safety recall campaigns for a vehicle.
Free US vehicle averages in USD from matched asking prices. VIN optional; limited public pilot.
Add one secure layer between your agents and this server.
