ShipMyCar Vehicle Logistics Quote Connector

Server Details

UK/EU and international car transport quotes with HMRC, IVA, DVLA and logistics costings.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 37 days
Last Tested: 2026-09-23 06:05
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.4/5.0

Scored 2026-09-11 00:11 across 3 tools

Disambiguation5/5

Each tool maps to a distinct stage in the quote workflow: updating draft details, checking draft requirements, and generating the final quote. There is no overlap in purpose or side effects.

Naming Consistency5/5

All tools share the 'quote_' prefix and use clear verb-led action names: generate, get_requirements, update_draft. The pattern is consistent and predictable.

Tool Count4/5

Three tools fit a focused quote-connector workflow without being bloated. The count is slightly minimal but appropriate for the narrow scope described.

Completeness4/5

The set covers the core lifecycle of draft update, requirement validation, and quote generation. Missing operations like retrieving a previously generated quote or managing bookings are outside the stated connector purpose, so only a minor gap exists.

Available Tools

3 tools

quote_generateGenerate quoteAInspect

Use this after the user explicitly confirms a complete ShipMyCar quote draft. It calculates pricing, writes a private quote continuation/API usage record, and returns a continueQuoteUrl. It does not send email or create a public booking.

ParametersJSON Schema

Name	Required	Description
`draft`	Yes	Complete MCP quote draft.
`confirm`	Yes	Must be true to generate the quote.
`contactConsent`	No	Set true only when the user consents to storing supplied contact details in the continuation payload.

Output Schema

ParametersJSON Schema

Name	Required	Description
`code`	No
`draft`	Yes
`quote`	No
`status`	No
`details`	No
`message`	No
`success`	Yes
`requirements`	No

TDQS

A4.5/5.0

Behavior5/5

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

Description details side effects (calculates pricing, writes record, returns URL) and clearly states what it does NOT do. Annotations show readOnlyHint=false, destructiveHint=false, consistent with writing a record. Provides context beyond annotations.

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?

Two sentences, no wasted words. First sentence covers purpose and timing, second covers exclusions. Highly efficient and easy to parse.

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 3 parameters, present siblings, and existing output schema, the description covers purpose, usage timing, behavior, and limitations comprehensively. No gaps noted.

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?

All 3 parameters have schema descriptions (100% coverage). Description adds context about 'complete draft' and consent requirement but does not significantly enhance parameter meaning beyond the schema. Adequate baseline given 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?

Description clearly states verb 'generate' on resource 'quote' with specific context 'after user explicitly confirms a complete ShipMyCar quote draft'. Distinguishes from sibling tools (quote_get_requirements, quote_update_draft) by focusing on final generation step.

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?

Explicitly instructs when to use: after explicit user confirmation of a complete draft. Also states what it does not do (no email, no booking). Lacks explicit exclusions for other scenarios, but positive guidance is strong.

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

quote_get_requirementsGet quote requirementsA

Read-only

Inspect

Use this when a ShipMyCar quote draft needs checking before generation. It only inspects the draft and returns route requirements, enabled services, missing fields, and next questions.

ParametersJSON Schema

Name	Required	Description	Default
`draft`	Yes	Current MCP quote draft to inspect.

Output Schema

ParametersJSON Schema

Name	Required	Description
`draft`	Yes
`success`	Yes
`warnings`	Yes
`routeType`	Yes
`capability`	Yes
`missingFields`	Yes
`nextQuestions`	Yes
`readyForQuote`	Yes
`enabledRouteTypes`	Yes
`enabledServiceModules`	Yes
`requiredServiceModules`	Yes

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already indicate read-only and non-destructive; description adds that it 'only inspects' and details the return content (route requirements, enabled services, missing fields, next questions), providing rich behavioral context without contradiction.

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?

Two sentences, no wasted words, front-loaded with usage instruction and clear listing of return items.

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 presence of output schema, the description still covers purpose, usage, and key return elements. For a simple tool with one parameter and supportive annotations, this is complete.

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 has 100% coverage with a clear description of the single 'draft' parameter. The tool description does not add additional meaning beyond what the schema already provides, so baseline score of 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 inspects a quote draft and returns specific requirements, with a verb and resource that distinguishes it from siblings like quote_generate and quote_update_draft.

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?

Explicitly says when to use ('when checking before generation') and implies read-only, but does not explicitly state when not to use it or name alternatives beyond sibling listing.

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

quote_update_draftUpdate quote draftA

Read-only

Inspect

Use this when a user provides or corrects ShipMyCar quote details. It returns a stateless draft plus next questions and does not create records, send email, or contact ShipMyCar.

ParametersJSON Schema

Name	Required	Description	Default
`draft`	No	Current MCP quote draft returned by a previous tool call.
`patch`	Yes	New quote details collected from the user.

Output Schema

ParametersJSON Schema

Name	Required	Description
`draft`	Yes
`success`	Yes
`warnings`	Yes
`routeType`	Yes
`capability`	Yes
`missingFields`	Yes
`nextQuestions`	Yes
`readyForQuote`	Yes
`requiredServiceModules`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

Beyond readOnlyHint annotation, the description clarifies statelessness, no record creation, no email, no contact, adding useful behavioral 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?

Two sentences, no redundancy, front-loaded with usage condition, every sentence adds value.

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 annotations, full schema coverage, and output schema existence, the description sufficiently covers purpose, usage, and behavioral details for this low-complexity tool.

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% with parameter descriptions; the tool description adds no extra parameter meaning beyond what schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (updating draft) and resource (quote details), and specifies what the tool does and does not do, differentiating it from potential sibling tools like quote_generate.

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?

Explicitly says when to use ('when user provides or corrects quote details') but does not provide when-not-to-use or mention sibling alternatives directly.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesJun 4, 2026

Changedquote_generate1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "details": {},
+    "draft": {},
+    "message": {
+      "type": "string"
+    },
+    "quote": {},
+    "requirements": {},
+    "status": {
+      "type": "number"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "draft"
+  ],
+  "type": "object"
+}

Changedquote_get_requirements1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "capability": {},
+    "draft": {},
+    "enabledRouteTypes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "enabledServiceModules": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missingFields": {
+      "items": {},
+      "type": "array"
+    },
+    "nextQuestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "readyForQuote": {
+      "type": "boolean"
+    },
+    "requiredServiceModules": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "routeType": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "success",
+    "draft",
+    "routeType",
+    "capability",
+    "readyForQuote",
+    "requiredServiceModules",
+    "missingFields",
+    "nextQuestions",
+    "warnings",
+    "enabledRouteTypes",
+    "enabledServiceModules"
+  ],
+  "type": "object"
+}

Changedquote_update_draft1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "capability": {},
+    "draft": {},
+    "missingFields": {
+      "items": {},
+      "type": "array"
+    },
+    "nextQuestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "readyForQuote": {
+      "type": "boolean"
+    },
+    "requiredServiceModules": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "routeType": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "success",
+    "draft",
+    "routeType",
+    "capability",
+    "readyForQuote",
+    "requiredServiceModules",
+    "missingFields",
+    "nextQuestions",
+    "warnings"
+  ],
+  "type": "object"
+}

3 tool updatesJun 4, 2026
- First observedquote_generate
- First observedquote_get_requirements
- First observedquote_update_draft

Related MCP Connectors

mcp B
com.fromtocargo
European road freight and moving prices: quotes, dated price index, glossary, order submission
Travel & Transportation E-commerce & Retail
191
mcp A
io.github.claracarspt
Used & imported cars in Portugal: search stock, ISV/IUC tax calc, resale value, contact.
E-commerce & Retail Finance
1121
Autoza UK A
io.github.Screed369
UK used cars: road tax (VED), ULEZ charges, MOT dates, DVSA reliability, live dealer stock.
Open Data Travel & Transportation
81
site A
uk.co.carimportcalculator
Car Import Calculator: the site's own MCP server — calculator, enquiry (enquiry = a human...
Finance
51

Related MCP Servers

export_quote
Finance
yuyiming-ship-it
A
license
Not graded
quality
B
maintenance
Enables AI clients to compute auditable vehicle export quotes with consistent decimal rules, including request normalization, funder screening, validation, comparison, and MOSS export.
Updated 5 days ago (2026-09-18 08:06 UTC)
MIT
PackZoo
Travel & Transportation E-commerce & Retail
IAfanasov
A
license
B
quality
C
maintenance
Compare parcel and letter delivery prices across 60+ carriers in 27 European countries.
Updated 2 months ago (2026-07-14 06:26 UTC)
1
MIT
Airport Pickups London MCP
mfy-apl
F
license
Not graded
quality
D
maintenance
Enables AI agents to get fixed-price quotes and book London airport transfers, with flight validation and inter-agent communication via A2A protocol.
Updated 6 months ago (2026-03-11 22:27 UTC)
-
Adopte un Conteneur —official
Travel & Transportation Location Services
adopteunconteneur
F
license
Not graded
quality
D
maintenance
Calculate empty shipping container delivery costs in France. Automatically selects the optimal depot and returns real prices (without and with VAT).
Updated 4 months ago (2026-05-09 17:27 UTC)
-