Apibara Vehicle Auction Data

List auction locations

list_auction_locations

Read-onlyIdempotent

Use to resolve supported auction yards, branches or facilities and their location metadata. Use calculate_shipping when the user needs auction-to-port pricing instead.

Input Schema

TableJSON Schema

Name	Required	Description
`s`	No	Free-text location search, such as a facility name, city or supported location term.
`state`	No	Optional state or region filter, for example FL.
`country`	No	Optional country filter supported by the locations endpoint.
`platform`	No	Optional source selector: Copart or IAA / IAAI.

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.

Changed5 schema fields changedSep 22, 2026

addedInput schema / properties / country / description

Added value: +"Optional country filter supported by the locations endpoint."

addedInput schema / properties / platform / description

Added value: +"Optional source selector: Copart or IAA / IAAI."

addedInput schema / properties / s / description

Added value: +"Free-text location search, such as a facility name, city or supported location term."

addedInput schema / properties / state / description

Added value: +"Optional state or region filter, for example FL."

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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description is not required to restate those. It adds minimal behavioral context, only mentioning that it resolves 'supported' locations and returns 'location metadata'. Since the output schema exists, return details are covered. The description adds no extra behavioral disclosures like pagination, rate limits, or authentication requirements, so a 3 is appropriate.

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 a single, front-loaded sentence that delivers the purpose and the key alternative without any wasted words. It is concise and well-structured, earning every word.

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?

The tool has zero required parameters, an output schema, and comprehensive annotations, so the description does not need to explain return values or safety. It clearly states the primary use and a sibling alternative. It could optionally mention that all parameters are optional filters, but the schema already conveys that. The description is complete enough for an agent to call it 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?

Schema description coverage is 100%, so all four parameters (s, state, country, platform) have descriptive text in the schema. The description does not add any additional parameter semantics or clarify usage beyond what the schema already provides. Baseline 3 applies when the schema fully documents parameters.

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 states a specific verb ('resolve') and a precise resource ('supported auction yards, branches or facilities') along with their location metadata. It also explicitly differentiates from the sibling 'calculate_shipping' by naming it and the condition that selects it, making the tool's purpose unambiguous.

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?

The description explicitly states when to use this tool ('to resolve supported auction yards...') and provides an alternative with a clear condition ('Use calculate_shipping when the user needs auction-to-port pricing instead'). This leaves no inference needed for the primary decision point.

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?