ticket.values description tells agents to use a 'formValues' field that does not exist

What happens

src/schemas/ticket.ts documents values as:

Raw form field answers keyed by field name (e.g. {"dietary-needs": "Vegan"}). Agents using MCP should prefer passing formValues, which resolves field titles or IDs to field names automatically

There is no formValues field. It appears nowhere in the package except inside that sentence:

$ grep -rn "formValues" dist/ | wc -l
1
$ grep -rn "formValues:" dist/schemas/ | wc -l
0

Why it matters

The sentence is aimed specifically at MCP agents, and it is the kind of instruction a model follows literally. Because TicketCreateSchema is a plain z.object(), Zod strips unknown keys rather than rejecting them — so formValues is silently discarded, values is absent, and create returns success having dropped the attendee's form answers.

There is no error for a model to react to. The tool documentation actively steers callers into silent data loss, which is worse than having no description at all.

// what the description recommends
await Confetti.tickets.create(
  { eventId: 1, email: 'a@example.com', status: 'attending',
    sendEmailConfirmation: false, formValues: { 'dietary-needs': 'Vegan' } },
  { apiKey },
)
// -> succeeds; the answers are gone

Suggested fix

Either implement formValues as described, or drop the sentence and document values alone. If it refers to something planned, it should not ship as advice in a released package.

Worth a wider check: this is the only description we found making a claim the schema does not back, but nothing currently prevents another.

Start in src/schemas/ticket.ts and inspect the TicketCreateSchema definition alongside the values description. Verify whether formValues is supported anywhere in the package, then update the schema or documentation so the published guidance matches accepted input and answers are not silently discarded. Use the reported dist/ searches to confirm the stale reference is gone or backed by a real field.