Skip to main content
Glama
Sign In

Singapore Event Print & Merch Quotes

by io.github.connectivehub
OverviewDiscussionsAdmin
This connector has been deprecated

Renamed to Singapore Buying Desk. Replaced by https://glama.ai/mcp/connectors/com.connective-labs/sg-buying-desk.

Request a firm quote

request_quote
Destructive

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. Example input: {"items":["3 x HDMI cable 5m"],"needed_by":"2026-11-15","contact_email":"buyer@example.com"}.

Input Schema

NameRequiredDescriptionDefault
itemsNoFor a list request, the lines the buyer wants quoted, 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.
categoryNoFor a single-item request, the kind of product or print job being quoted. Leave it out when sending items or list_id.
quantityNoFor a single-item request, how many units the buyer wants quoted.
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_nameNoBuyer's name, used to address the firm quote.
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. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Single-item requests: the category. Not needed when items or list_id is given."New value: +"For a single-item request, the kind of product or print job being quoted. Leave it out when sending items or list_id."
    • changedInput schema / properties / items / description
      Previous value: -"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)."New value: +"For a list request, the lines the buyer wants quoted, 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)."
    • changedInput schema / properties / quantity / description
      Previous value: -"Single-item requests: number of units."New value: +"For a single-item request, how many units the buyer wants quoted."
  2. Changed1 schema field changed
    • addedInput schema / properties / contact_name / description
      Added value: +"Buyer's name, used to address the firm quote."
  3. 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"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "name-cards",
-  "lanyards",
-  "roll-up-banners",
-  "tote-bags",
-  "backdrops",
-  "event-merch",
-  "printed-collateral",
-  "office-it-supplies",
-  "packaging"
-]New value: +[
+  "office-it-supplies",
+  "name-cards",
+  "lanyards",
+  "roll-up-banners",
+  "tote-bags",
+  "backdrops",
+  "event-merch",
+  "printed-collateral",
+  "packaging"
+]
    • changedInput schema / properties / description / description
      Previous value: -"What is needed, with all known specs (size, material, finish, colours, artwork status)."New value: +"What is needed, with all known specs (brand, model, connectors, capacity, size, material, finish, colours, artwork status)."
  5. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "name-cards",
-  "lanyards",
-  "roll-up-banners",
-  "tote-bags",
-  "backdrops",
-  "event-merch",
-  "printed-collateral",
-  "packaging"
-]New value: +[
+  "name-cards",
+  "lanyards",
+  "roll-up-banners",
+  "tote-bags",
+  "backdrops",
+  "event-merch",
+  "printed-collateral",
+  "office-it-supplies",
+  "packaging"
+]
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial lifecycle context beyond the annotations: the tool returns a reference only, the firm price and date arrive by email usually same business day, nothing is charged until buyer approval, and delivery is Singapore only. It does not explain why destructiveHint=true or what state a submission mutates, nor whether resubmitting the same request creates duplicates (idempotentHint=false), leaving a small gap against the annotation profile.

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?

Purpose and routing lead the text before the use-case catalogue, and the closing example is compact. The middle sentence packs many product categories into one long clause, which is dense but each clause does narrow eligibility for an agent deciding whether to call this or an instant-quote sibling.

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, non-idempotent submission tool with no output schema, the description covers the important unknowns: what comes back (a reference), how the real answer is delivered (email, same business day), billing safety, and geographic scope. Minor omissions remain around what quantity/category imply for list requests and how duplicates are handled.

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 already 100%, so the baseline is 3, but the description adds genuine routing semantics: items and list_id are the list path, category/quantity/description are the single-item path, and items must have 'the same line items you gave quote_list'. The concrete example input {"items":["3 x HDMI cable 5m"],...} also disambiguates the anyOf string-or-object array shape.

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 differentiates itself from siblings by naming quote_list and quote_office_supplies as the paths it does NOT cover. An agent can tell what this tool is for without opening the 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?

Explicitly enumerates the two calling modes (single item via category/description/quantity, or a list via items/list_id) and then enumerates the use cases that trigger it: items not matched by quote_office_supplies, custom event print and merch, unusual specs, deadlines faster than instant options. Alternatives and the conditions selecting them are named rather than inferred.

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

All Singapore Event Print & Merch Quotes 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