Skip to main content
Glama

Singapore Buying Desk (Connective Labs)

by com.connective-labs
OverviewDiscussionsAdmin

Request a firm quote or place an order

request_quote

Submit a request for a firm quote. Use it for one item (category, description, quantity) or for a whole list: pass items (the same line items you gave quote_list) or the list_id that quote_list returned. Covers office or IT items not matched by quote_office_supplies, custom event print and merch (backdrops, signage, branded merch, flyers, packaging), unusual specs, deadlines faster than any instant option, and orders for instantly priced items. Returns a reference; a firm price and date is sent to the contact email, usually the same business day. Nothing is charged until the buyer approves the firm quote. Singapore delivery only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoList requests: line items, each a string like '2 x HDMI cable 5m' or an object with item, quantity and optional category, brand, model, specs (same shape as quote_list).
companyNoBuyer's company, if any.
list_idNoList requests: the list_id returned by quote_list (valid 14 days). Its lines are used when items is not given.
categoryNoSingle-item requests: the category. Not needed when items or list_id is given.
quantityNoSingle-item requests: number of units.
needed_byYesDeadline date, YYYY-MM-DD.
budget_sgdNoOptional maximum budget in SGD.
descriptionNoSingle-item requests: what is needed, with all known specs (brand, model, connectors, capacity, size, material, finish, colours, artwork status). For a list, any overall notes.
contact_nameNo
contact_emailYesWhere to send the firm quote.
delivery_locationNoDelivery address or area in Singapore, or 'self-collect'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Single-item requests: the category. Not needed when items or list_id is given."
    • addedInput schema / properties / company
      Added value: +{
+  "description": "Buyer's company, if any.",
+  "type": "string"
+}
    • changedInput schema / properties / description / description
      Previous value: -"What is needed, with all known specs (brand, model, connectors, capacity, size, material, finish, colours, artwork status)."New value: +"Single-item requests: what is needed, with all known specs (brand, model, connectors, capacity, size, material, finish, colours, artwork status). For a list, any overall notes."
    • addedInput schema / properties / items
      Added value: +{
+  "description": "List requests: line items, each a string like '2 x HDMI cable 5m' or an object with item, quantity and optional category, brand, model, specs (same shape as quote_list).",
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "object"
+      }
+    ]
+  },
+  "maxItems": 50,
+  "type": "array"
+}
    • addedInput schema / properties / list_id
      Added value: +{
+  "description": "List requests: the list_id returned by quote_list (valid 14 days). Its lines are used when items is not given.",
+  "type": "string"
+}
    • addedInput schema / properties / quantity / description
      Added value: +"Single-item requests: number of units."
    • changedInput schema / required
      Previous value: -[
-  "category",
-  "description",
-  "quantity",
-  "needed_by",
-  "contact_email"
-]New value: +[
+  "needed_by",
+  "contact_email"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description adds workflow context they do not: a reference is returned, the firm price and date arrive by contact email usually the same business day, nothing is charged until the buyer approves, and delivery is Singapore-only. That is genuinely useful post-submission behavior. It stops short of five because it does not address whether resubmitting duplicates a request, even though idempotentHint=false.

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 the core purpose in the first sentence, then adds usage, return behavior, charging, and geography in a tight paragraph. Long but nearly every sentence carries information an agent needs; only the sibling enumeration borders on list-like density.

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 an 11-parameter mutation tool with no output schema, the description covers the input modes, what is returned (a reference), how the firm quote reaches the buyer, cost implications, and the Singapore-only constraint. What remains unexplained is mostly handled by the high-coverage schema, so it is complete enough to call correctly.

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 description coverage is 91%, so the baseline is 3 and the schema already documents most fields. The description adds routing meaning the schema lacks on its own: items must be "the same line items you gave quote_list," list_id comes from quote_list, and category/quantity/description are single-item-only, which clarifies the mutually exclusive modes.

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 and resource ("Submit a request for a firm quote") and immediately contrasts its scope with siblings: it covers what quote_office_supplies doesn't match, plus custom print/merch and orders for instantly priced items. An agent can tell it apart from quote_list, quote_office_supplies, and quote_event_print without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit about the two invocation modes (single item vs whole list) and which field selects each. It enumerates the concrete situations that route here: unmatched office/IT items, custom event print and merch, unusual specs, deadlines faster than any instant option, and orders of instantly priced items. Nothing is left to inference.

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

All Singapore Buying Desk (Connective Labs) 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