Standard Titanium Quotations

Request a multi-line titanium quotation

request_quote

Submit one or more structured titanium line items for quotation review. Each item may include sectionShape (ROUND, HEX, FLAT or UNKNOWN). Only call after the customer has reviewed all interpreted items and explicitly agreed to submit them.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	Customer's email address
`items`	Yes	One or more structured titanium requirements. Include sectionShape where relevant.
`customerName`	Yes	Customer's full name
`deliveryLocation`	Yes	Delivery location or postcode

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`createdAt`	Yes
`enquiryId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 17, 2026

addedInput schema / properties / deliveryLocation

Added value: +{
+  "description": "Delivery location or postcode",
+  "type": "string"
+}

removedInput schema / properties / description

Removed value: -{
-  "description": "Detailed description of what the customer needs",
-  "type": "string"
-}

addedInput schema / properties / items

Added value: +{
+  "description": "One or more structured titanium requirements. Include sectionShape where relevant.",
+  "items": {
+    "properties": {
+      "additionalRequirements": {
+        "type": "string"
+      },
+      "alloy": {
+        "type": "string"
+      },
+      "certification": {
+        "type": "string"
+      },
+      "destination": {
+        "type": "string"
+      },
+      "dimensions": {
+        "properties": {
+          "diameterMm": {
+            "type": "number"
+          },
+          "insideDiameterMm": {
+            "type": "number"
+          },
+          "lengthMm": {
+            "type": "number"
+          },
+          "outsideDiameterMm": {
+            "type": "number"
+          },
+          "thicknessMm": {
+            "type": "number"
+          },
+          "wallThicknessMm": {
+            "type": "number"
+          },
+          "widthMm": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "grade": {
+        "type": "string"
+      },
+      "productForm": {
+        "enum": [
+          "SHEET",
+          "PLATE",
+          "ROUND_BAR",
+          "FLAT_BAR",
+          "TUBE",
+          "PIPE",
+          "WIRE",
+          "FORGING",
+          "FASTENER",
+          "OTHER",
+          "UNKNOWN"
+        ],
+        "type": "string"
+      },
+      "quantity": {
+        "type": "number"
+      },
+      "quantityUnit": {
+        "enum": [
+          "PIECES",
+          "KG",
+          "TONNES",
+          "METRES",
+          "LENGTHS",
+          "SHEETS",
+          "PLATES",
+          "BARS",
+          "UNKNOWN"
+        ],
+        "type": "string"
+      },
+      "requiredDate": {
+        "format": "date",
+        "type": "string"
+      },
+      "sectionShape": {
+        "type": "string"
+      },
+      "specification": {
+        "type": "string"
+      },
+      "surfaceFinish": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "dimensions",
+      "productForm",
+      "quantity",
+      "quantityUnit"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedInput schema / properties / postcode

Removed value: -{
-  "description": "Postcode for the service or delivery location",
-  "type": "string"
-}

removedInput schema / properties / service

Removed value: -{
-  "description": "Short name of the service or product being quoted",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "customerName",
-  "email",
-  "postcode",
-  "service",
-  "description"
-]New value: +[
+  "customerName",
+  "email",
+  "deliveryLocation",
+  "items"
+]

changedOutput schema / properties / status / enum

Previous value: -[
-  "PENDING_PRICING",
-  "INFORMATION_REQUIRED",
-  "QUOTED",
-  "CANCELLED"
-]New value: +[
+  "PENDING_PRICING",
+  "PENDING_REVIEW",
+  "INFORMATION_REQUIRED",
+  "QUOTED",
+  "CANCELLED"
+]

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already communicate that this is not read-only and not idempotent. The description adds meaningful context by framing the call as a "quotation review" step and requiring explicit customer agreement before submission, which is a valuable guardrail beyond what the annotations provide.

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 two sentences with no filler. It front-loads the main purpose and immediately follows with the key usage constraint, making it easy for an agent to parse quickly and accurately.

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 tool with a nested items schema, annotations, and an output schema, the description is largely complete: it states the scope, the submission precondition, and the domain. It does not explicitly describe what happens after submission or point to get_quote_status, but the sibling name and output schema cover most of that gap.

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 for the four top-level parameters is 100%, so the baseline is 3. The description adds one useful detail by enumerating sectionShape values (ROUND, HEX, FLAT, UNKNOWN), but it does not explain the required item fields or other parameter meanings, leaving the schema to carry most of the semantic load.

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 uses a specific verb and resource: "Submit one or more structured titanium line items for quotation review." This clearly identifies both the action and the object, and it is easy to distinguish from the sibling get_quote_status because one creates a request while the other checks status.

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?

The description gives a clear precondition: "Only call after the customer has reviewed all interpreted items and explicitly agreed to submit them." This effectively tells the agent when not to call, but it does not explicitly mention get_quote_status or outline when that alternative should be used instead.

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

All Standard Titanium Quotations tools Inspect

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

Need Help?