Sense2 Promotional Products

quote_options

Read-only

ONE-CALL buyer quote: 'best price on N , needed by '. Searches the catalogue, prices each match at the buyer's quantity (or at the product's minimum order when N is below MOQ, with the MOQ stated plainly), ranks by total spend, and returns 3-8 options with unit price, setup, total (tax-exclusive, in the locale currency), MOQ status, production window and a DISPATCH note. needBy (YYYY-MM-DD) returns which options' production windows fit before that date — dispatch only; freight is quoted per job and Sense2 never promises a delivery date. Prefer this over search_products→get_quote chains.

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": {
      "query": "<query>",
      "quantity": "<quantity>"
    },
    "name": "quote_options"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Options to return, 1-8 (default 5)
`query`	Yes	Product type or keywords, e.g. 'notebooks', 'eco tote bags'
`locale`	No	en-AU (default), en-US, en-NZ, de-DE, ja-JP
`needBy`	No	Optional YYYY-MM-DD the buyer is working towards; answered as which production windows fit before it (dispatch, not arrival)
`quantity`	Yes	Units the buyer wants (positive integer)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / needBy / description

Previous value: -"Optional YYYY-MM-DD the buyer needs the goods in hand"New value: +"Optional YYYY-MM-DD the buyer is working towards; answered as which production windows fit before it (dispatch, not arrival)"

AddedSep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the read-only and closed-world annotations, it discloses the full pipeline: catalogue search, quantity/MOQ pricing, total-spend ranking, option count, returned fields, and the important caveat that needBy covers dispatch only and never a delivery promise. This is exactly the behavioral context an agent needs to call it correctly.

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?

The core purpose and buyer pattern are front-loaded in the opening clause. It is dense but mostly earned; some clauses could be broken out for readability, and the 'ONE-CALL' emphasis is repeated by the final sentence, but there is little true waste.

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?

For a multi-step quote tool with no output schema and minimal annotations, the description supplies enough context: number of options returned, currency and tax treatment, ranking logic, MOQ handling, production-window filtering, and dispatch-only caveat. Nothing material is missing for correct invocation.

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 baseline is 3, but the description adds meaning by explaining that quantity below MOQ is priced at the product's minimum order and the MOQ is stated, and it clarifies needBy as a dispatch-fit filter. Those additions go beyond the schema's brief parameter notes.

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 states a specific verb and resource ('ONE-CALL buyer quote'), names the exact input pattern, and contrasts the tool with the search_products→get_quote chain. An agent can immediately distinguish it from ordinary search or single-quote tools.

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?

It explicitly says 'Prefer this over search_products→get_quote chains', which names the alternative and the condition that selects this tool. The buyer scenario ('best price on N <product type>, needed by <date>') gives a concrete when-to-use trigger.

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

All Sense2 Promotional Products 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?