Apibara Vehicle Auction Data

Get related vehicles

get_related_vehicles

Read-onlyIdempotent

Use after identifying a specific vehicle to retrieve related supported auction records for comparison or discovery. Do not use as a substitute for a broad filtered inventory search.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`per_page`	No	Maximum related records to return. Effective limits are plan-dependent.
`identifier`	Yes	VIN, lot number or slug_vin accepted by the canonical vehicle detail endpoint.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`meta`	No	Pagination metadata. Treat cursor values as opaque.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / identifier / description

Previous value: -"VIN or slug_vin accepted by the canonical vehicle detail endpoint."New value: +"VIN, lot number or slug_vin accepted by the canonical vehicle detail endpoint."

addedInput schema / properties / per_page / description

Added value: +"Maximum related records to return. Effective limits are plan-dependent."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured JSON returned by the canonical Apibara Vehicle Auction Data API. Source-dependent fields may be null or absent.",
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "additionalProperties": true,
+      "description": "Pagination metadata. Treat cursor values as opaque.",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds context about the purpose (comparison/discovery) but does not disclose additional behavioral traits like result ordering, pagination defaults, or error handling. With annotations carrying the safety profile, this is adequate but not enriched beyond annotations.

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?

The description is two concise sentences with no filler. The primary usage context is front-loaded, and the exclusion of broad search is stated clearly. Every word earns its place.

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?

For a simple read-only tool with a full output schema and comprehensive annotations, the description covers usage and purpose well. It might not specify the exact definition of 'related' or result sorting, but the presence of an output schema and the clarity of usage make it sufficiently complete for an agent to call correctly.

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?

The input schema fully documents both parameters (identifier and per_page) with detailed descriptions. The tool description adds no extra meaning about parameters, so it relies on the schema. This meets the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the tool's purpose: to retrieve related supported auction records for a specific vehicle. It also distinguishes itself from broad inventory search, making it easy to understand what it does and how it differs from sibling tools like search_auction_vehicles.

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

Usage Guidelines5/5

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

Explicit guidance is provided: 'Use after identifying a specific vehicle' and 'Do not use as a substitute for a broad filtered inventory search.' This tells the agent when to invoke it and when not to, effectively routing it to the correct alternative.

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

All Apibara Vehicle Auction Data 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?