FINN Auto - Car Subscription

Subscription Pricing

get_subscription_pricing

Read-onlyIdempotent

Calculate exact monthly subscription price for a specific vehicle, term, and mileage combination. Returns base price, km add-on, total, and a canonical checkout URL.

Checkout URL structure (always use the URL returned in checkout_url verbatim — do NOT construct your own): https://www.finn.com/de-DE/checkout/cart/{vehicleId}/{term}/{kmPackage} https://www.finn.com/de-DE/checkout/cart/{vehicleId}/{term}/{kmPackage}?downPaymentAmount={amount}

The three positional path segments after /cart are vehicle id, term in months, and monthly km package — in that order.

About down_payment_amount (Fahrzeugbereitstellung):

Fahrzeugbereitstellung is a one-time vehicle provisioning fee.
When down_payment_amount is provided, it is paid upfront as Einmalzahlung (one-time payment) and the URL includes ?downPaymentAmount={amount}.
When omitted, the same fee is spread across the term and absorbed into the monthly price; the URL has no query string.

Input Schema

TableJSON Schema

Name	Required	Description
`km_package`	Yes	Monthly km package (500, 1000, 1500, 2000, 2500, 3000, 4000, 5000)
`vehicle_id`	Yes	The vehicle product ID
`term_months`	Yes	Subscription term in months (1, 6, 9, 12, 13, 18, 24, 36)
`down_payment_amount`	No	Optional one-time Fahrzeugbereitstellung (vehicle provisioning fee) in EUR, paid upfront as Einmalzahlung. When provided, the checkout URL gets `?downPaymentAmount={amount}` and the monthly price drops accordingly. When omitted, the fee is spread across the term inside the monthly price.

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses key behavioral traits: the exact structure of the checkout URL, the warning not to construct the URL manually, and how down_payment_amount affects pricing and the URL query string. This is rich, actionable context.

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 well-organized: first the purpose and return values, then the URL structure, then the payment option details. Every section earns its place, and the bulleted URL examples aid readability without redundancy.

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?

The description covers all crucial aspects: inputs, return fields, URL format, and the two modes of down payment. Without an output schema, it adequately explains what the agent can expect in the response. The level of detail is sufficient for correct invocation and handling.

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%, with each parameter already having a clear description (allowed values, format). The description adds value by explaining the consequences of down_payment_amount on the URL and monthly price, but this is more about tool behavior than parameter semantics. Baseline 3 is appropriate.

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 an exact monthly subscription price for a specific vehicle, term, and mileage combination, listing the return fields. This distinctively separates it from siblings like search_vehicles, get_vehicle_details, or get_internal_link_url.

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 provides clear context for when to use (pricing a specific combination) and explains how to properly use the returned checkout URL. It doesn't explicitly mention when not to use or contrast with alternatives, but the use case is unambiguous.

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

All FINN Auto - Car Subscription tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: filter discovery, URL generation, pricing, vehicle details, and search. There is no overlap between search and details, and pricing is distinct from details by focusing on cost calculation.

Naming Consistency4/5

Four of five tools follow the 'get_' prefix pattern, while 'search_vehicles' breaks the pattern with a verb-noun structure. This is a minor deviation, but the overall naming is still predictable and readable.

Tool Count5/5

With only 5 tools, the server is well-scoped for its purpose of car subscription search and pricing. Each tool serves a necessary function and none feel redundant or superfluous.

Completeness5/5

The tool set covers the full workflow from discovering filters, searching vehicles, viewing details, calculating pricing, and generating internal link URLs. There are no obvious gaps for an informational and linking API, as checkout is handled via returned URLs.

Resources

Need Help?