Sense2 Promotional Products

get_product

Read-only

Get full product details by PID (branded pricing; plus a wholesale block with unbranded, no-setup prices where plain stock is available). locale localises the product name, currency, pricing and URL (en-AU, en-US, en-NZ, de-DE, ja-JP); descriptions are English for all locales.

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": {
      "pid": "<pid>"
    },
    "name": "get_product"
  }
}

Input Schema

Name	Required	Description	Default
`pid`	Yes	Product ID (number or string)
`locale`	No	Locale (en-AU, en-US, en-NZ, de-DE, ja-JP). Localises name/currency/URL; description stays English.	en-AU

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / pid / description

Previous value: -"Product ID"New value: +"Product ID (number or string)"

changedInput schema / properties / pid / type

Previous value: -"number"New value: +[
+  "string",
+  "number"
+]

Changed1 schema field changedAug 4, 2026

changedInput schema / properties / locale / description

Previous value: -"Locale (en-AU, en-US, en-NZ, de-DE, ja-JP)"New value: +"Locale (en-AU, en-US, en-NZ, de-DE, ja-JP). Localises name/currency/URL; description stays English."

First observedJul 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real content beyond them: the response carries branded pricing plus an optional wholesale block, and wholesale prices exist only 'where plain stock is available'. The locale note also discloses precisely which fields change and which stay English, which is exactly the kind of behavior an agent cannot get from the schema.

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?

Two sentences, front-loaded with the core action and the payload highlights, with no filler. The heavy parentheticals are dense but every clause (wholesale availability condition, locale scope) carries information an agent would otherwise have to guess.

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?

With no output schema, the description must characterize the return value, and it does — branded pricing, a conditional wholesale block, and localized fields. It stops short of describing the full object structure, but for a two-parameter read tool that is a minor gap.

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 description coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description adds one useful nuance — that pricing (not just name/currency/URL) is localized — but otherwise largely restates the schema's locale list and English-description caveat.

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?

The description states a specific verb and resource ('Get full product details by PID') and even previews the shape of the payload (branded pricing plus a wholesale block). It does not name search_products as the way to discover PIDs, so sibling differentiation is only implied rather than stated.

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?

Usage is implied by the 'by PID' framing — you need an identifier in hand — but there is no explicit when-to-use/when-not guidance and no pointer to search_products for finding a PID. An agent can infer the context but must do the routing itself.

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?