Sense2 Promotional Products

get_collections

Read-only

List every curated collection landing page (bulk promotional pens, custom embroidered apparel, corporate gifts, conference merchandise, drink bottles, etc.) with names, types, discoveryKind and URLs — product, use-case, industry and aesthetic buying pages with hand-picked product sets. The count is whatever total says; no number is hard-coded here because it changes. Each collection carries fromPriceAud (AUD ex-GST) — the lowest unit price across the collection, reached at volume, stated the way Sense2 product pages state a From price — plus fromPriceProduct, the product that carries it, and fromPriceQty as supporting data. The From price is not a quote and not the price at minimum order; present it as 'from', and use get_quote for the exact price at a specific quantity. PAGED (default 50 per page, max 200): returns total, returned, offset, hasMore and nextOffset — call again with offset=nextOffset for the next page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_collections"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Entries per page (default 50, max 200)
`offset`	No	Skip the first N entries (default 0) — use nextOffset from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Entries per page (default 50, max 200)",
+  "type": "number"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip the first N entries (default 0) — use nextOffset from the previous page",
+  "type": "number"
+}

AddedAug 31, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, yet the description adds substantial behavioral context: the count is dynamic (read total, nothing hard-coded), fromPriceAud is AUD ex-GST at volume and is explicitly not a quote nor the minimum-order price, and the tool is paged at 50/200 with hasMore and nextOffset semantics. This is exactly the kind of caveat an agent needs to avoid misreporting a price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the single dense paragraph mixes return fields, price semantics and paging into one block, and the meta aside ('no number is hard-coded here because it changes') does little work. The fromPrice discussion is long yet justified since there is no output schema.

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?

With no output schema and only two trivial params, the description carries return-value disclosure well: it names names/types/discoveryKind/URLs, the fromPrice trio, and the full paging envelope (total, returned, offset, hasMore, nextOffset). Nothing an agent needs to call and interpret it correctly is missing.

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 is 100% and both parameters already document default 50 / max 200 and 'use nextOffset from the previous page'. The description restates those values and the offset=nextOffset pattern without adding syntax or edge-case behavior, so the schema does the heavy lifting and baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List every ... buying pages') and enumerates what each record contains (types, discoveryKind, URLs, hand-picked product sets). It clearly distinguishes itself from get_quote but never differentiates from the singular sibling get_collection, so an agent must infer the bulk-vs-single split.

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

Usage Guidelines3/5

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

Guidance exists but is narrow: it routes exact quantity pricing to get_quote and explains the paging loop. It gives no explicit when-to-use/when-not guidance against the closely named siblings get_collection and get_cheapest_by_collection, leaving the main routing decision implicit.

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?