Skip to main content
Glama
Sign In

Lenius

by app.lenius
OverviewDiscussionsAdmin

Quote order

quote_order
Read-onlyIdempotent

Price an order exactly like the shop checkout (lines, fees, discounts, total in DKK incl. VAT), check that the time, products, minimum order and delivery address are OK, and tell how it is paid. Nothing is saved. Shows a card with the products (with their images), fees and total so the customer can see what they are ordering; show the result to the customer before place_order.

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD (from available_times)
shopNoThe "shop" value from find_shops (not needed on a shop's own address <shop>.lenius.app/mcp)
timeYesHH:MM (from available_times)
itemsYes
addressNoRequired for delivery
fulfillmentYes
other_stopsNoThe other orders you are placing for the customer in this conversation (other shops, same day): used only to warn when they are too far apart in time (trip_warnings). Nothing is looked up about the customer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / other_stops
      Added value: +{
+  "description": "The other orders you are placing for the customer in this conversation (other shops, same day): used only to warn when they are too far apart in time (trip_warnings). Nothing is looked up about the customer.",
+  "items": {
+    "properties": {
+      "address": {
+        "description": "Required for delivery",
+        "properties": {
+          "city": {
+            "maxLength": 60,
+            "minLength": 2,
+            "type": "string"
+          },
+          "postal_code": {
+            "maxLength": 10,
+            "minLength": 3,
+            "type": "string"
+          },
+          "street": {
+            "description": "Street and number",
+            "maxLength": 120,
+            "minLength": 2,
+            "type": "string"
+          }
+        },
+        "required": [
+          "street",
+          "postal_code",
+          "city"
+        ],
+        "type": "object"
+      },
+      "date": {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "fulfillment": {
+        "enum": [
+          "pickup",
+          "delivery"
+        ],
+        "type": "string"
+      },
+      "shop": {
+        "description": "The \"shop\" value from find_shops",
+        "maxLength": 100,
+        "minLength": 1,
+        "type": "string"
+      },
+      "time": {
+        "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "shop",
+      "fulfillment",
+      "date",
+      "time"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / items / items / properties / options / description
      Previous value: -"Answers to the product's options from get_menu (option_id + choice_id, or option_id + text). Required options must be answered; ask the customer, never pick for them."New value: +"Answers to the product's options from get_menu (option_id + choice_id, option_id + text, or option_id + choices for choose_many). Required options must be answered; ask the customer, never pick for them."
    • changedInput schema / properties / items / items / properties / options / items / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "choice_id": {
-        "description": "choice_id from get_menu",
-        "maxLength": 32,
-        "minLength": 1,
-        "type": "string"
-      },
-      "option_id": {
-        "maxLength": 32,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "option_id",
-      "choice_id"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "option_id": {
-        "maxLength": 32,
-        "minLength": 1,
-        "type": "string"
-      },
-      "text": {
-        "description": "The customer's own words, e.g. \"uden løg\"",
-        "maxLength": 500,
-        "type": "string"
-      }
-    },
-    "required": [
-      "option_id",
-      "text"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "choice_id": {
+        "description": "choice_id from get_menu",
+        "maxLength": 32,
+        "minLength": 1,
+        "type": "string"
+      },
+      "option_id": {
+        "maxLength": 32,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "option_id",
+      "choice_id"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "option_id": {
+        "maxLength": 32,
+        "minLength": 1,
+        "type": "string"
+      },
+      "text": {
+        "description": "The customer's own words, e.g. \"uden løg\"",
+        "maxLength": 500,
+        "type": "string"
+      }
+    },
+    "required": [
+      "option_id",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "choices": {
+        "description": "choose_many: the chosen choices; the total must be between min_total and max_total",
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "choice_id": {
+              "maxLength": 32,
+              "minLength": 1,
+              "type": "string"
+            },
+            "quantity": {
+              "description": "1 unless the option has quantities",
+              "maximum": 100,
+              "minimum": 1,
+              "type": "integer"
+            }
+          },
+          "required": [
+            "choice_id",
+            "quantity"
+          ],
+          "type": "object"
+        },
+        "maxItems": 100,
+        "type": "array"
+      },
+      "option_id": {
+        "maxLength": 32,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "option_id",
+      "choices"
+    ],
+    "type": "object"
+  }
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / options
      Added value: +{
+  "description": "Answers to the product's options from get_menu (option_id + choice_id, or option_id + text). Required options must be answered; ask the customer, never pick for them.",
+  "items": {
+    "anyOf": [
+      {
+        "additionalProperties": false,
+        "properties": {
+          "choice_id": {
+            "description": "choice_id from get_menu",
+            "maxLength": 32,
+            "minLength": 1,
+            "type": "string"
+          },
+          "option_id": {
+            "maxLength": 32,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "option_id",
+          "choice_id"
+        ],
+        "type": "object"
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "option_id": {
+            "maxLength": 32,
+            "minLength": 1,
+            "type": "string"
+          },
+          "text": {
+            "description": "The customer's own words, e.g. \"uden løg\"",
+            "maxLength": 500,
+            "type": "string"
+          }
+        },
+        "required": [
+          "option_id",
+          "text"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  "maxItems": 20,
+  "type": "array"
+}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description reinforces with 'Nothing is saved' and adds valuable output context (a card with product images, fees, and total) that annotations do not convey. It also flags validation behavior (checks time, products, minimum order, address), though it does not mention the trip_warnings output the schema hints at.

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?

Information-dense and mostly front-loaded: pricing scope first, then validation, then the no-persistence note and the workflow instruction. The long third sentence is somewhat run-on but each clause carries distinct value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with nested objects and no output schema, the description covers purpose, validation, persistence, and the shape of the returned card well enough to call it correctly. Minor gap: it doesn't surface the trip_warnings/warning behavior implied by other_stops.

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 71%, so most parameters (date/time from available_times, items options, address for delivery, other_stops) are already documented in the schema. The description restates the validated concerns (time, products, minimum order, address) but adds no syntax or format detail beyond the schema, so 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?

States a specific verb (price/quote) plus resource (order) and scope (lines, fees, discounts, total in DKK incl. VAT), and explicitly distinguishes itself from the sibling place_order by naming it as the follow-up step. An agent can tell it apart from place_order and order_status without opening either schema.

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?

Clearly routes the agent: quote first, show the customer, then call place_order. The 'Nothing is saved' framing implies this is the non-committing preview versus the committing sibling. It lacks an explicit 'do not use for X' exclusion, but the workflow context is unambiguous.

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

All Lenius toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources