What should a reseller expose in a public preview or MCP listing?

**What belongs in a public preview?**

A preview can describe the workflow boundary, role model, input schema, supported actions and intended customer use. It can also show a generated demonstration case whose public status is explicit in the release metadata.

**Should the preview include a worked answer?**

A worked answer can help customers understand the task, provided the demonstration is separated from cases intended for protected evaluation. Publicly exposing a solution changes how that case should be used, even if the underlying record identifiers are later renamed.

**What should an MCP listing communicate?**

It should distinguish descriptive resources from executable environment tools and identify which resources contain demonstrations. A discovery resource should not imply that reading a public sample grants redistribution rights to the wider product.

**What is the useful first request?**

Ask for a proposed public-preview manifest and its relationship to the licensed pack. Resellers can inspect whether website text, exports and MCP resources reveal consistent scope while preserving the intended separation between demonstration content and protected evaluation material.