Tools reference
The three kinds of tool AI Desk exposes over MCP, what each costs, and the scope that unlocks it.
Tools reference
Everything AI Desk does is exposed as an MCP tool. There are three kinds, and they behave differently enough that it is worth knowing which you are calling.
Report tools
The 23 finished reports. Each one runs analysis, writes a hosted HTML page you can share, and returns a structured summary. These are what most people mean by AI Desk.
Priced per run or per unit, listed on each report's page in the catalog. Scope is reports:<report-name>.
Data tools
Raw access to the underlying dataset, for the follow-up question a finished report does not answer. "Show me the actual listings behind that number" is the typical case.
They return JSON. No hosted page, no narration, no analysis.
| Tool | Scope | Price |
|---|---|---|
search_active_cars |
data:search-active-cars |
$0.01 per call |
search_past_90_days |
data:search-past-90-days |
$0.02 per call |
get_car_history |
data:get-car-history |
$0.02 per call |
decode_vin_neovin |
data:decode-vin-neovin |
$0.16 per call |
predict_price_with_comparables |
data:predict-price-with-comparables |
$0.18 per call |
get_market_insights (Beta) |
data:get-market-insights |
varies by request |
Two things to know about pricing here. These are the Starter pay-as-you-go rates from the API rate card, which is the undiscounted column: there is no monthly commitment, so there is no commitment discount. And get_market_insights is priced by the shape of the request rather than per call, because one question can span a little or a lot of data.
Each tool carries its own scope, so an agent can be granted raw search without being granted VIN decoding.
System tools
Account and support functions. Free, and they need a connected account rather than a scope.
| Tool | What it does |
|---|---|
get_account_status |
Balance, auto top-up settings, payment method on file |
add_credits |
Top up the balance |
update_auto_topup |
Set the threshold and refill amount |
list_recent_reports |
What has run recently |
list_invoices / get_invoice |
Billing history |
get_payment_method |
The card on file |
list_available_reports |
The catalog with current prices |
create_support_ticket |
Raise an issue |
submit_feedback |
Tell us something |
get_help |
What this product is and how to use it |
update_auto_topup is the one worth calling early. For an unattended integration it is the difference between a service that keeps running and one that silently stops at a zero balance.
Scopes
A scope is one permission for one tool. Nothing is implied: granting reports:vehicle-valuation-report does not grant data:search-active-cars.
Where scopes are set depends on who is calling:
- A person in a chat client approves scopes on the consent screen when they connect, and can change them later under their account connections.
- An agent (a backend service) is granted scopes when you create it, and can be edited afterwards.
An agent can never widen its own scopes. A token request asking for more than the agent holds returns only the intersection, silently, so check the scope field on the token response if a call is refused unexpectedly.
Calling a tool
Every tool is called the same way, over POST https://ai.marketcheck.com/mcp:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_account_status",
"arguments": {}
}
}
The result arrives as result.content[0].text, holding JSON as a string. Parse it.
See Server-side access for the token exchange, and each report's page for its arguments.