vivid-ads-commerce

vivid_request_quote

Email the customer a formal QUOTATION. If the exact configuration can be priced and an email is given, this INSTANTLY emails a branded PDF-style quotation (line items, GST, total, quote number, 14-day validity, accept-online link) — status 'quoted'. For custom/unpriceable products it logs the request for the team to prepare and send (status 'received'). Never takes payment. Confirm product, quantity, size/options, name, and email before submitting.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`size`	No
`email`	Yes
`phone`	No	customer phone (optional)
`design`	No	design preference: 'ai_design' \| 'upload_own' \| 'design_later'
`company`	No
`message`	No	the customer's full request in their own words (multi-item OK)
`options`	No	FULL selected options (same shape as vivid_price.options) so the quotation is priced exactly — include size + any dropdowns/add-ons.
`product`	No
`quantity`	No
`artworkUrl`	No	link to the customer's uploaded artwork (e.g. the fileUrl returned by vivid_upload_artwork), if any
`discountCode`	No	any reseller/trade or discount code the customer mentioned (recorded, NOT applied here)

TDQS

A4.5/5.0

Behavior5/5

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

Discloses significant behavioral context beyond annotations: instantly emails a branded PDF, sets status to 'quoted' or 'received', never takes payment, and includes 14-day validity and accept-online link. No contradiction with the annotations (mutating, non-idempotent, open-world).

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

Conciseness5/5

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

Four sentences, front-loaded with the core purpose, followed by conditional behavior and a final confirmation checklist. No filler or repetition of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and no output schema, the description covers inputs, conditional behavior, side effects, and exclusions well, but does not describe the return value/response (e.g., quote ID or confirmation). It also does not explicitly handle the missing-email case beyond the stated condition, leaving a 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?

Description names the key parameters to confirm (product, quantity, size/options, name, email), clarifies discountCode is recorded but not applied, and references artworkUrl as the upload link. This adds meaning beyond the schema, especially with only 50% schema coverage, though design, phone, company, and message are left to schema.

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?

Clearly states the tool emails a formal quotation, distinguishing it from pricing/order/accept tools by specifying the branded PDF, statuses, and 'Never takes payment.' The conditional quoted/received behavior further clarifies scope.

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?

Provides clear context: use when a customer requests a formal quotation and details are confirmed, with an explicit fallback for custom/unpriceable items and an explicit exclusion that payment is not taken. However, it does not name sibling alternatives like vivid_price or vivid_accept_quote, so it stops short of full when-not guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation2/5

Several tools have overlapping purposes, particularly order status (vivid_order_status vs vivid_fulfilment_order_status vs vivid_fulfilment_production_stage) and artwork handling (vivid_artwork vs vivid_upload_artwork). An agent could easily select the wrong one without careful reading of the descriptions.

Naming Consistency4/5

All tools share the consistent 'vivid_' prefix and snake_case format. However, the second part mixes verb-noun patterns (place_order, check_artwork) with noun-based names (price, product, order_status), so the pattern isn't fully uniform but is still predictable and readable.

Tool Count3/5

At 25 tools, the server is at the heavy end of the borderline range. The broad scope (product discovery, pricing, ordering, artwork, fulfilment statuses, support) justifies most tools, but some overlapping status/artwork tools could be consolidated to reduce clutter.

Completeness4/5

The server covers the entire customer journey from product search, configuration, pricing, quoting, ordering, artwork upload/check, proof tracking, production/delivery status, to reordering. Minor gaps like explicit order update/cancel tools are missing, but support_answer covers those topics and the lifecycle is otherwise well-covered.

Resources

Need Help?