Apibara Vehicle Auction Data

Calculate auction-to-port shipping

calculate_shipping

Read-onlyIdempotent

Use when the user asks for supported auction-to-port shipping pricing for a known vehicle. Supply either VIN or lot_number; optionally narrow the destination with port or port_id. Availability depends on auction location and route data.

Input Schema

TableJSON Schema

Name	Required	Description
`vin`	No	Vehicle Identification Number. Provide this or lot_number.
`port`	No	Optional destination port name supported by the shipping endpoint.
`port_id`	No	Optional destination port identifier when known.
`lot_number`	No	Auction lot number. Provide this or vin.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 22, 2026

addedInput schema / properties / lot_number / description

Added value: +"Auction lot number. Provide this or vin."

addedInput schema / properties / port / description

Added value: +"Optional destination port name supported by the shipping endpoint."

addedInput schema / properties / port_id / description

Added value: +"Optional destination port identifier when known."

addedInput schema / properties / vin / description

Added value: +"Vehicle Identification Number. Provide this or lot_number."

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"
+    }
+  },
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat those. It adds valuable context by noting 'Availability depends on auction location and route data,' which is a behavioral constraint beyond what annotations convey. This enriches the agent's understanding of potential failure or limitation.

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 three concise sentences, all relevant and front-loaded with the usage trigger. It contains no fluff, and every sentence adds value—usage condition, input requirements, and an availability caveat. It is appropriately sized for the tool's complexity.

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

Completeness5/5

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

Given the tool has an output schema and only 4 parameters, the description covers all necessary invocation details: when to use, what inputs to supply, and a caveat about availability. Nothing critical is missing, and the output schema handles return value expectations.

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%, so all parameters are documented in the schema. The description repeats the essential choice between VIN and lot_number and mentions optional port/port_id, but it adds no deeper semantic detail (e.g., precedence, format constraints, or how port_id relates to port). This is 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 calculates shipping pricing for a known vehicle to a port, using a specific verb and resource. It distinguishes from siblings like get_vehicle or search_auction_vehicles by focusing on shipping, and it specifies the input requirements (VIN or lot number).

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?

The description explicitly says 'Use when the user asks for supported auction-to-port shipping pricing for a known vehicle,' providing a clear trigger condition. It also mentions optional narrowing with port or port_id, but it does not explicitly list when not to use it or alternatives. However, since siblings are unrelated to shipping, the guidance is sufficient.

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?