vivid-ads-commerce

Get a live price

vivid_price

Read-onlyIdempotent

Calculate the current price for an EXACT product configuration. Pass options with the full selected configuration (use vivid_product first), or just size for simple products. Some products take several seconds or need manual confirmation. Before calling, briefly tell the customer you're checking the live price. Never estimate or reuse another configuration's price. When presenting, repeat the exact product title, quantity, dimensions, and price-affecting options.

Input Schema

Name	Required	Description
`size`	No	(simple products) size, e.g. '850x2000', or a named size like 'medium'
`options`	No	FULL selected options keyed by the schema keys from vivid_product, e.g. { size:'Medium', sides:'Double-sided', base:'Heavy Duty Metal Plate (5kg)' } or { size:'Custom', widthMm:700, heightMm:1000, eyelets:'4 x eyelets (all corners)', cutting:'Square or Rectangle' }
`product`	Yes	product name, e.g. 'pull up banner', 'corflute', 'a-frame', 'feather flag'
`quantity`	No	how many

Output Schema

Name	Required	Description
`size`	No
`sizes`	No
`addOns`	No
`status`	Yes	outcome discriminator, e.g. ok / priced / need_size / manual_quote / unknown_product / error
`message`	No
`product`	No
`summary`	No
`currency`	No
`quantity`	No
`unitPrice`	No	AUD, GST-inclusive
`agent_note`	No
`totalPrice`	No	AUD, GST-inclusive
`gstIncluded`	No
`tierApplied`	No
`assumedOptions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 20, 2026

addedInput schema / properties / quantity / maximum
```
Added value: +100000
```
addedInput schema / properties / quantity / minimum
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "addOns": {},
+    "agent_note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "assumedOptions": {},
+    "currency": {},
+    "gstIncluded": {},
+    "message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "product": {},
+    "quantity": {},
+    "size": {},
+    "sizes": {},
+    "status": {
+      "description": "outcome discriminator, e.g. ok / priced / need_size / manual_quote / unknown_product / error",
+      "type": "string"
+    },
+    "summary": {},
+    "tierApplied": {},
+    "totalPrice": {
+      "description": "AUD, GST-inclusive",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "unitPrice": {
+      "description": "AUD, GST-inclusive",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedJul 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds meaningful operational traits beyond them: variable latency ('several seconds'), possible manual confirmation, and the rule never to estimate or reuse another configuration's price. It doesn't cover failure modes or what happens on an invalid configuration, so not a 5.

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?

Front-loaded with the core purpose, then prerequisites, then latency, then customer-presentation rules. Every sentence carries an instruction an agent needs, though the customer-communication directives make it slightly long relative to the pure selection guidance.

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?

An output schema exists, so return values needn't be described, and the definition covers the tricky parts of a nested-`options` pricing call: prerequisite tool, exact-config requirement, latency, and presentation. Error/validation behavior is the only notable gap.

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 baseline is 3, but the description adds real meaning: it explains that `options` keys must be the FULL configuration drawn from vivid_product's schema, and that `size` alone suffices for simple products. That relationship between the two parameters isn't expressible in the schema itself.

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 ('Calculate the current price') scoped to an 'EXACT product configuration', which distinguishes it from estimate/price-break siblings like vivid_price_breaks and vivid_delivery_quote. It also names the upstream dependency (vivid_product), so an agent can place it correctly in a workflow.

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?

Gives clear context: use vivid_product first, pass full `options` for configurable products or just `size` for simple ones, and warn the customer before a slow call. It does not explicitly state when to prefer this over vivid_price_breaks or vivid_request_quote, so it stops short of full alternative routing.

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

All vivid-ads-commerce 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?