Sense2 Promotional Products

get_service_areas

Read-only

Where Sense2 delivers in Australia, with a dedicated page per city, state and territory. Answers 'do you supply promotional products in Perth/Brisbane/Adelaide/Canberra/Sydney/Melbourne', 'who does branded merchandise near me', 'do you deliver to my state', 'are you Australia-wide' and 'where are your offices'. Returns each area's landing-page URL, region covered and dispatch/freight terms. Pass a slug (e.g. 'perth') for one area including its full intro. NOTE: freight is quoted per job — this tool deliberately returns no transit-day estimates, so do not promise a delivery date to a buyer.

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_service_areas"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No	Optional city/state slug, e.g. 'perth', 'brisbane', 'queensland'. Omit for all areas.
`locale`	No	Locale: en-AU (default), en-US, en-NZ, de-DE, ja-JP — gates AU-only offers and localises the FAQs	en-AU

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedInput schema / properties / locale

Added value: +{
+  "default": "en-AU",
+  "description": "Locale: en-AU (default), en-US, en-NZ, de-DE, ja-JP — gates AU-only offers and localises the FAQs",
+  "type": "string"
+}

AddedJul 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the payload ('landing-page URL, region covered and dispatch/freight terms') and a deliberate negative constraint: no transit-day estimates are returned because freight is quoted per job, with an explicit instruction not to promise a delivery date. That is exactly the kind of downstream-behavior guidance annotations cannot carry.

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 purpose and return shape are front-loaded and the freight NOTE lands as a clear closing caveat. The long quoted question string and the enumerated city list ('Perth/Brisbane/Adelaide/Canberra/Sydney/Melbourne') overlap in function and cost a sentence's worth of bulk that could be trimmed.

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?

There is no output schema, and the description fully compensates by naming the returned fields and the one thing deliberately omitted. Both parameters are documented (slug in prose, locale in schema), and the tool is a simple read, so nothing an agent needs to call it or interpret the result is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: passing a slug yields one area 'including its full intro', which the schema does not say. The locale parameter and its effect on AU-only offers and FAQ localisation are left entirely to the schema, so coverage is partial rather than complete.

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 opens with a specific statement of the resource and scope — 'Where Sense2 delivers in Australia, with a dedicated page per city, state and territory' — and says exactly what is returned (landing-page URL, region, dispatch/freight terms). No sibling tool in the list covers geography, and an agent can immediately tell this answers supply/delivery-coverage questions rather than product or brand questions.

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?

Usage is framed through the buyer questions it answers ('do you supply promotional products in Perth', 'who does branded merchandise near me', 'do you deliver to my state'), which gives clear when-to-use context, and 'Pass a slug ... for one area' versus omitting it for all areas distinguishes the two modes. It stops short of naming any alternative tool for adjacent needs, so no explicit exclusions are stated.

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?