Skip to main content
Glama

MapleV Tesla Collision Parts

Get delivery options for a city

get_delivery_options
Read-only

Given a delivery city anywhere in Canada (province recommended), return MapleV's delivery options with ETA, cut-off time and CAD fee. Inside the local delivery area (Metro Vancouver and the Fraser Valley, BC): same-day and next-day delivery, plus 2-hour rush in the metro core. Everywhere else in Canada: ground courier with the typical transit time for the destination province, freight quoted at checkout. Answers questions like 'can MapleV get this part to my shop in Abbotsford today?' or 'how long does shipping to Calgary take?'. Fees are customer-facing CAD; local delivery is free on orders at or above the published threshold, and courier shipping is free from CA$300 to a BC address and CA$500 to any other province (after discounts; bumper covers excepted); Yukon, the Northwest Territories and Nunavut pay the carrier's rate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "get_delivery_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesDelivery city, e.g. 'Burnaby', 'Abbotsford', 'Calgary', 'Toronto'.
provinceNoProvince or territory, as a code or name ('BC', 'Alberta', 'Québec'). Give it for any city outside Metro Vancouver: the transit estimate is per province, and without it a city outside the local BC delivery area gets only a generic ground-courier answer.
orderSubtotalCADNoOrder subtotal in CAD, used only to show whether the free-delivery threshold is met. Defaults to 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"Delivery city, e.g. 'Burnaby', 'Abbotsford', 'Victoria'."New value: +"Delivery city, e.g. 'Burnaby', 'Abbotsford', 'Calgary', 'Toronto'."
    • changedInput schema / properties / province / description
      Previous value: -"Province or territory. Defaults to BC; anything outside BC is quoted as freight."New value: +"Province or territory, as a code or name ('BC', 'Alberta', 'Québec'). Give it for any city outside Metro Vancouver: the transit estimate is per province, and without it a city outside the local BC delivery area gets only a generic ground-courier answer."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations by disclosing the service tiers themselves (same-day, next-day, 2-hour rush in the metro core, ground courier elsewhere, freight quoted at checkout), cut-off times, and the exact free-delivery thresholds with post-discount rules and a bumper-cover exception. It also flags that the territories pay the carrier's rate. This is the kind of domain behavior an agent could not infer from annotations.

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?

Front-loads what the tool returns before layering coverage areas, example questions, and fee rules, and every sentence carries operational information. It is dense rather than padded, though the single-paragraph fee clause with nested exceptions is heavy to parse in one read.

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?

With no output schema, the description still specifies the return payload (ETA, cut-off time, CAD fee) and how it varies by region, so an agent knows what to expect. The one unexplained annotation-level detail, idempotentHint=false, is not contradicted and matters little for a read-only quote lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema carries the baseline; the description nevertheless adds meaning by explaining why province changes the answer (per-province transit estimate, generic ground-courier result without it) and by enumerating the free-delivery thresholds that orderSubtotalCAD is tested against, including discount timing and the bumper-cover exclusion.

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?

Opens with a specific verb+resource (return MapleV's delivery options) scoped to a delivery city in Canada, and enumerates the returned attributes (ETA, cut-off time, CAD fee). The three sibling tools (get_part, search_parts, list_categories) are catalog lookups, so this is clearly distinguishable as a logistics/quote tool.

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 frames the intended questions ('can MapleV get this part to my shop in Abbotsford today?', 'how long does shipping to Calgary take?') and states province is recommended for cities outside Metro Vancouver because transit is estimated per province. It does not name alternative tools or state exclusions, but the sibling catalog tools are unrelated enough that no routing conflict exists.

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