Skip to main content
Glama

ExoticCar.Loans: exotic and classic car loan calculator

Published depreciation figures by model

get_car_depreciation
Read-onlyIdempotent

Published five-year depreciation figures for exotic and luxury models (iSeeCars 2026 study and iSeeCars modeled estimates) annualized the way the calculator uses them, plus Hagerty Price Guide quarterly collector-value changes, each with source, period and date. Search by make or model, or omit query for every row.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_car_depreciation"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoMake or model to search for, e.g. "Porsche", "911", "Urus". Omit for all rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds useful context about sources, periods, dates, annualization, and that omitting the query returns every row. It stops short of describing pagination or result-size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and sources are front-loaded, and the second sentence gives the query behavior. It is dense but efficient, with no clearly wasted sentences.

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?

For a read-only lookup with one optional parameter and no output schema, the description is complete enough: it identifies the data sources, the period basis, and the row-level metadata the agent will receive.

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 coverage is 100% and the single query parameter is already documented in the schema. The description reinforces make/model search and full-table fallback but adds no new syntax or filtering details beyond the schema.

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 names a specific resource (published five-year depreciation figures for exotic and luxury models) and sources (iSeeCars, Hagerty), which clearly separates it from the loan-calculation siblings. An agent can tell this is a data lookup, not a calculator.

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?

It explains how to use the tool: search by make or model, or omit query for all rows. That gives clear operating context, though it does not explicitly state when to prefer this over the loan-related siblings or any exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources