Deoochform

Create form

create_form

Create a new form and return its public link. A form is a page of questions that collects answers. An animated wedding invitation page is a different object, built by create_invitation, and the phrase "wedding invitation form" usually describes that page rather than a questionnaire.

Input Schema

TableJSON Schema

Name	Required	Description
`rules`	No	Conditional show/hide logic: each rule reads one field's answer and shows or hides another. Only set this when asked for a field to depend on another; most forms carry no rules. Every fieldId used must exist in this same `fields` array, a rule referencing a field that isn't there is dropped.
`theme`	No	Visual preset: the form's entire look, not only its background colour. DESIGNED PRESETS (typography, field styling, depth and background together): `editorial`: warm paper, serif title, understated. This is the answer when the user asks for something beautiful, premium, elegant, polished, smart or professional without naming a colour. Category presets, each with its own title font; pick by what the form is for: `blush`: weddings, engagements, beauty, celebrations. `bistro`: restaurants, cafes, catering, food orders, hotels. `playground`: schools, courses, kids' classes, summer camps. `studio`: gyms, fitness classes, sport, races (dark). `clinic`: healthcare, dental, therapy, patient intake. `noir`: tattoo, photography, music, creative studios (dark). `chambers`: law, accountancy, consulting, anything that ends in a signature. `terminal`: engineering, IT, bug reports, internal tooling (dark). `meadow`: charities, community groups, volunteering, the environment. `civic`: councils, school offices, public services, official reports. `frost`: winter events, travel, and anything that should feel cool and unhurried. These show a cover photo behind the title when the form has one. SCENES (a photograph behind the form, with the card tinted to match it). Reach for one when the form is for a real place or occasion and the user wants it to feel like that place. All are dark: `lane`: pools, gyms, swimming, anything with water. `skyline`: property, architecture, city and office work. `ceremony`: weddings and formal invitations. `nightfield`: festivals, gigs, outdoor events after dark. `kiln`: studios, workshops, craft and making things by hand. `confetti`: parties, birthdays, celebrations. `supper`: restaurants, reservations, hospitality. `roastery`: cafes, coffee, drink orders. `expedition`: tours, travel, the outdoors. `salon`: salons, barbers, beauty appointments. `thermal`: spas, treatments, rest. `lecture`: courses, training, teaching. `atrium`: clinics and practices, calm and clinical. `marquee`: conferences, talks, ticketed events. `trailhead`: races, runs, outdoor signups. `pressroom`: photography, press, creative bookings. A scene carries a photograph the user did not choose, so prefer a category preset unless they asked for imagery or described a setting. PLAIN: `default` (warm neutral, standard field styling). The flat colour palettes that used to sit here are retired: they still render on forms that already use them, but nothing should pick one now. How to choose: - They named a colour → the category preset or scene closest to it. - The form clearly belongs to one of the categories above → that category preset. - They asked for it to look good but named no colour → `editorial`. - They asked for neither → OMIT. A form nobody asked to style stays default. Each preset is a matched set and cannot be mixed or set piecemeal. If the user asked for something none of these express (a specific hex value, two colours combined, a particular font), apply the nearest and tell them plainly what you could and couldn't do.
`title`	Yes
`fields`	No	Do not open with a `heading` field that repeats the form title. The title already renders above the fields. Use `heading` fields only to break a multi-topic form into named sections. For anything the respondent attaches from their device (a CV, resume, photo, receipt, portfolio) the type is `upload`, never `file`. `file` is a plain URL text box and collects no file at all. A `label` or `helpText` may quote an earlier answer back to the respondent by writing `{{<field id>}}`, e.g. a field with id `q1` asking their name lets a later label read `Thanks {{q1}}, what is your email?`. The reference is the other field's id, never its label, and that field must appear earlier in this same `fields` array; add `\|` and fallback text (`{{q1\|there}}`) for what to show when they skipped it. A reference naming a field that is not in this array is rejected.
`layout`	No	How the form presents itself. `classic` stacks every question on one page and is the default. `conversational` asks one question per screen, with a progress bar and Next/Back. Set `conversational` when the user asks for one question at a time, a guided or step-by-step form, or something that feels like a conversation; it pairs especially well with labels that quote an earlier answer. It changes nothing about what is collected, so it is safe to set on a form that already has responses.
`description`	No
`submitLabel`	No	Text on the final button, at most 40 characters. Write what pressing it does, in the form's own voice: "Book my table", "Count me in", "Send my RSVP". Omit for "Submit". Ignored on payment forms, whose button always states the amount.
`templateSlug`	No	Start from one of the ready made templates; list_templates returns the slugs. A template brings its own field set, colour theme and header artwork, which hand written fields don't include. Omit `fields` to take the template's as-is; supply `fields` only to genuinely replace them, which loses the template's questions but keeps its theme and artwork.
`notAnInvitation`	No	Leave this out. Set it to true only after the user has been told about the interactive invitation page and has explicitly said they want a plain questionnaire instead.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes
`theme`	Yes
`formId`	Yes
`publicUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / layout / description

Previous value: -"How the form presents itself. `classic` stacks every question on one page and is the default. `conversational` asks one question per screen, with a progress bar and Next/Back, the Typeform-style flow. Set `conversational` when the user asks for one question at a time, a guided or step-by-step form, or something that feels like a conversation; it pairs especially well with labels that quote an earlier answer. It changes nothing about what is collected, so it is safe to set on a form that already has responses."New value: +"How the form presents itself. `classic` stacks every question on one page and is the default. `conversational` asks one question per screen, with a progress bar and Next/Back. Set `conversational` when the user asks for one question at a time, a guided or step-by-step form, or something that feels like a conversation; it pairs especially well with labels that quote an earlier answer. It changes nothing about what is collected, so it is safe to set on a form that already has responses."

changedInput schema / properties / templateSlug / description

Previous value: -"Start from one of our ready-made templates. Call list_templates to find the slug. STRONGLY PREFERRED over writing fields by hand whenever a template fits: the template brings its own field set, colour theme and header artwork, none of which you can supply yourself. Omit `fields` to take the template's as-is; supply `fields` only to genuinely replace them, which loses the template's questions but keeps its theme and artwork."New value: +"Start from one of the ready made templates; list_templates returns the slugs. A template brings its own field set, colour theme and header artwork, which hand written fields don't include. Omit `fields` to take the template's as-is; supply `fields` only to genuinely replace them, which loses the template's questions but keeps its theme and artwork."

Changed3 schema fields changedSep 25, 2026

addedInput schema / properties / fields / items / properties / formula
```
Added value: +{
+  "maxLength": 500,
+  "type": "string"
+}
```

changedInput schema / properties / fields / items / properties / type / description

Previous value: -"The field's input type. Two of these are easily confused: `upload` is the real file uploader, the respondent attaches an image, PDF or Word doc from their device, and is what you want for a CV, resume, photo, receipt, portfolio, certificate, or any \"attach\"/\"upload\" request. `file` is NOT an uploader: it only collects a URL the respondent types in, so use it only when the user explicitly asked for a link to a file hosted somewhere else."New value: +"The field's input type. Two of these are easily confused: `upload` is the real file uploader, the respondent attaches an image, PDF or Word doc from their device, and is what you want for a CV, resume, photo, receipt, portfolio, certificate, or any \"attach\"/\"upload\" request. `file` is NOT an uploader: it only collects a URL the respondent types in, so use it only when the user explicitly asked for a link to a file hosted somewhere else. `calculation` shows a number worked out from other answers, such as a total or a score; its `formula` holds arithmetic (+ - * /, brackets, round, min, max) over other fields referenced as {{<field id>}}, e.g. \"{{qty}} * 25\". A choice answer counts as the first number in its text."

changedInput schema / properties / fields / items / properties / type / enum

Previous value: -[
-  "text",
-  "textarea",
-  "name",
-  "email",
-  "phone",
-  "url",
-  "address",
-  "number",
-  "select",
-  "radio",
-  "checkbox",
-  "ranking",
-  "rating",
-  "scale",
-  "date",
-  "time",
-  "file",
-  "upload",
-  "signature",
-  "appointment",
-  "heading",
-  "image",
-  "page-break",
-  "hidden"
-]New value: +[
+  "text",
+  "textarea",
+  "name",
+  "email",
+  "phone",
+  "url",
+  "address",
+  "number",
+  "select",
+  "radio",
+  "checkbox",
+  "ranking",
+  "rating",
+  "scale",
+  "date",
+  "time",
+  "file",
+  "upload",
+  "signature",
+  "appointment",
+  "heading",
+  "image",
+  "page-break",
+  "hidden",
+  "calculation"
+]

Changed2 schema fields changedSep 18, 2026

changedInput schema / properties / theme / description

Previous value: -"Visual preset: the form's entire look, not only its background colour.\n\nDESIGNED PRESETS (typography, field styling, depth and background together):\n`editorial`: warm paper, serif title, understated. This is the answer when the user asks for something beautiful, premium, elegant, polished, smart or professional without naming a colour.\nCategory presets, each with its own title font; pick by what the form is for:\n`blush`: weddings, engagements, beauty, celebrations.\n`bistro`: restaurants, cafes, catering, food orders, hotels.\n`playground`: schools, courses, kids' classes, summer camps.\n`studio`: gyms, fitness classes, sport, races (dark).\n`clinic`: healthcare, dental, therapy, patient intake.\n`noir`: tattoo, photography, music, creative studios (dark).\nThese show a cover photo behind the title when the form has one.\n\nSCENES (a photograph behind the form, with the card tinted to match it). Reach for one when the form is for a real place or occasion and the user wants it to feel like that place. All are dark:\n`lane`: pools, gyms, swimming, anything with water.\n`skyline`: property, architecture, city and office work.\n`ceremony`: weddings and formal invitations.\n`nightfield`: festivals, gigs, outdoor events after dark.\n`kiln`: studios, workshops, craft and making things by hand.\n`confetti`: parties, birthdays, celebrations.\n`supper`: restaurants, reservations, hospitality.\n`roastery`: cafes, coffee, drink orders.\n`expedition`: tours, travel, the outdoors.\n`salon`: salons, barbers, beauty appointments.\n`thermal`: spas, treatments, rest.\n`lecture`: courses, training, teaching.\n`atrium`: clinics and practices, calm and clinical.\n`marquee`: conferences, talks, ticketed events.\n`trailhead`: races, runs, outdoor signups.\n`pressroom`: photography, press, creative bookings.\nA scene carries a photograph the user did not choose, so prefer a category preset unless they asked for imagery or described a setting.\n\nPLAIN:\n`default` (warm neutral, standard field styling). The flat colour palettes that used to sit here are retired: they still render on forms that already use them, but nothing should pick one now.\n\nHow to choose:\n- They named a colour → the category preset or scene closest to it.\n- The form clearly belongs to one of the categories above → that category preset.\n- They asked for it to look good but named no colour → `editorial`.\n- They asked for neither → OMIT. A form nobody asked to style stays default.\n\nEach preset is a matched set and cannot be mixed or set piecemeal. If the user asked for something none of these express (a specific hex value, two colours combined, a particular font), apply the nearest and tell them plainly what you could and couldn't do."New value: +"Visual preset: the form's entire look, not only its background colour.\n\nDESIGNED PRESETS (typography, field styling, depth and background together):\n`editorial`: warm paper, serif title, understated. This is the answer when the user asks for something beautiful, premium, elegant, polished, smart or professional without naming a colour.\nCategory presets, each with its own title font; pick by what the form is for:\n`blush`: weddings, engagements, beauty, celebrations.\n`bistro`: restaurants, cafes, catering, food orders, hotels.\n`playground`: schools, courses, kids' classes, summer camps.\n`studio`: gyms, fitness classes, sport, races (dark).\n`clinic`: healthcare, dental, therapy, patient intake.\n`noir`: tattoo, photography, music, creative studios (dark).\n`chambers`: law, accountancy, consulting, anything that ends in a signature.\n`terminal`: engineering, IT, bug reports, internal tooling (dark).\n`meadow`: charities, community groups, volunteering, the environment.\n`civic`: councils, school offices, public services, official reports.\n`frost`: winter events, travel, and anything that should feel cool and unhurried.\nThese show a cover photo behind the title when the form has one.\n\nSCENES (a photograph behind the form, with the card tinted to match it). Reach for one when the form is for a real place or occasion and the user wants it to feel like that place. All are dark:\n`lane`: pools, gyms, swimming, anything with water.\n`skyline`: property, architecture, city and office work.\n`ceremony`: weddings and formal invitations.\n`nightfield`: festivals, gigs, outdoor events after dark.\n`kiln`: studios, workshops, craft and making things by hand.\n`confetti`: parties, birthdays, celebrations.\n`supper`: restaurants, reservations, hospitality.\n`roastery`: cafes, coffee, drink orders.\n`expedition`: tours, travel, the outdoors.\n`salon`: salons, barbers, beauty appointments.\n`thermal`: spas, treatments, rest.\n`lecture`: courses, training, teaching.\n`atrium`: clinics and practices, calm and clinical.\n`marquee`: conferences, talks, ticketed events.\n`trailhead`: races, runs, outdoor signups.\n`pressroom`: photography, press, creative bookings.\nA scene carries a photograph the user did not choose, so prefer a category preset unless they asked for imagery or described a setting.\n\nPLAIN:\n`default` (warm neutral, standard field styling). The flat colour palettes that used to sit here are retired: they still render on forms that already use them, but nothing should pick one now.\n\nHow to choose:\n- They named a colour → the category preset or scene closest to it.\n- The form clearly belongs to one of the categories above → that category preset.\n- They asked for it to look good but named no colour → `editorial`.\n- They asked for neither → OMIT. A form nobody asked to style stays default.\n\nEach preset is a matched set and cannot be mixed or set piecemeal. If the user asked for something none of these express (a specific hex value, two colours combined, a particular font), apply the nearest and tell them plainly what you could and couldn't do."

changedInput schema / properties / theme / enum

Previous value: -[
-  "default",
-  "editorial",
-  "blush",
-  "bistro",
-  "playground",
-  "studio",
-  "clinic",
-  "noir",
-  "lane",
-  "skyline",
-  "ceremony",
-  "nightfield",
-  "kiln",
-  "confetti",
-  "supper",
-  "roastery",
-  "expedition",
-  "salon",
-  "thermal",
-  "lecture",
-  "atrium",
-  "marquee",
-  "trailhead",
-  "pressroom"
-]New value: +[
+  "default",
+  "editorial",
+  "blush",
+  "bistro",
+  "playground",
+  "studio",
+  "clinic",
+  "noir",
+  "lane",
+  "skyline",
+  "ceremony",
+  "nightfield",
+  "kiln",
+  "confetti",
+  "supper",
+  "roastery",
+  "expedition",
+  "salon",
+  "thermal",
+  "lecture",
+  "atrium",
+  "marquee",
+  "trailhead",
+  "pressroom",
+  "chambers",
+  "terminal",
+  "meadow",
+  "civic",
+  "frost"
+]

Changed2 schema fields changedSep 17, 2026

changedInput schema / properties / theme / description

Previous value: -"Visual preset: the form's entire look, not only its background colour.\n\nDESIGNED PRESETS (typography, field styling, depth and background together):\n`editorial`: warm paper, serif title, understated. This is the answer when the user asks for something beautiful, premium, elegant, polished, smart or professional without naming a colour.\nCategory presets, each with its own title font; pick by what the form is for:\n`blush`: weddings, engagements, beauty, celebrations.\n`bistro`: restaurants, cafes, catering, food orders, hotels.\n`playground`: schools, courses, kids' classes, summer camps.\n`studio`: gyms, fitness classes, sport, races (dark).\n`clinic`: healthcare, dental, therapy, patient intake.\n`noir`: tattoo, photography, music, creative studios (dark).\nThese show a cover photo behind the title when the form has one.\n\nCOLOUR PALETTES (background and button colour only, default field styling):\n`default` (warm neutral), `midnight`/`ink` (dark), `royal`/`ocean` (blue), `forest` (green), `sunset` (orange), `rose` (pink), `plum` (purple), `slate` (grey).\n\nHow to choose:\n- They named a colour → that palette.\n- The form clearly belongs to one of the categories above → that category preset.\n- They asked for it to look good but named no colour → `editorial`.\n- They asked for neither → OMIT. A form nobody asked to style stays default.\n\nEach preset is a matched set and cannot be mixed or set piecemeal. If the user asked for something none of these express (a specific hex value, two colours combined, a particular font), apply the nearest and tell them plainly what you could and couldn't do."New value: +"Visual preset: the form's entire look, not only its background colour.\n\nDESIGNED PRESETS (typography, field styling, depth and background together):\n`editorial`: warm paper, serif title, understated. This is the answer when the user asks for something beautiful, premium, elegant, polished, smart or professional without naming a colour.\nCategory presets, each with its own title font; pick by what the form is for:\n`blush`: weddings, engagements, beauty, celebrations.\n`bistro`: restaurants, cafes, catering, food orders, hotels.\n`playground`: schools, courses, kids' classes, summer camps.\n`studio`: gyms, fitness classes, sport, races (dark).\n`clinic`: healthcare, dental, therapy, patient intake.\n`noir`: tattoo, photography, music, creative studios (dark).\nThese show a cover photo behind the title when the form has one.\n\nSCENES (a photograph behind the form, with the card tinted to match it). Reach for one when the form is for a real place or occasion and the user wants it to feel like that place. All are dark:\n`lane`: pools, gyms, swimming, anything with water.\n`skyline`: property, architecture, city and office work.\n`ceremony`: weddings and formal invitations.\n`nightfield`: festivals, gigs, outdoor events after dark.\n`kiln`: studios, workshops, craft and making things by hand.\n`confetti`: parties, birthdays, celebrations.\n`supper`: restaurants, reservations, hospitality.\n`roastery`: cafes, coffee, drink orders.\n`expedition`: tours, travel, the outdoors.\n`salon`: salons, barbers, beauty appointments.\n`thermal`: spas, treatments, rest.\n`lecture`: courses, training, teaching.\n`atrium`: clinics and practices, calm and clinical.\n`marquee`: conferences, talks, ticketed events.\n`trailhead`: races, runs, outdoor signups.\n`pressroom`: photography, press, creative bookings.\nA scene carries a photograph the user did not choose, so prefer a category preset unless they asked for imagery or described a setting.\n\nPLAIN:\n`default` (warm neutral, standard field styling). The flat colour palettes that used to sit here are retired: they still render on forms that already use them, but nothing should pick one now.\n\nHow to choose:\n- They named a colour → the category preset or scene closest to it.\n- The form clearly belongs to one of the categories above → that category preset.\n- They asked for it to look good but named no colour → `editorial`.\n- They asked for neither → OMIT. A form nobody asked to style stays default.\n\nEach preset is a matched set and cannot be mixed or set piecemeal. If the user asked for something none of these express (a specific hex value, two colours combined, a particular font), apply the nearest and tell them plainly what you could and couldn't do."

changedInput schema / properties / theme / enum

Previous value: -[
-  "default",
-  "midnight",
-  "royal",
-  "forest",
-  "ocean",
-  "sunset",
-  "rose",
-  "plum",
-  "slate",
-  "ink",
-  "editorial",
-  "blush",
-  "bistro",
-  "playground",
-  "studio",
-  "clinic",
-  "noir"
-]New value: +[
+  "default",
+  "editorial",
+  "blush",
+  "bistro",
+  "playground",
+  "studio",
+  "clinic",
+  "noir",
+  "lane",
+  "skyline",
+  "ceremony",
+  "nightfield",
+  "kiln",
+  "confetti",
+  "supper",
+  "roastery",
+  "expedition",
+  "salon",
+  "thermal",
+  "lecture",
+  "atrium",
+  "marquee",
+  "trailhead",
+  "pressroom"
+]

Changed2 schema fields changedSep 16, 2026

addedInput schema / properties / fields / items / properties / imageUrl

Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "pattern": "^\\/templates\\/(?:[a-z0-9-]+\\.svg|photos\\/[a-z0-9-]+\\.jpg)$",
+      "type": "string"
+    }
+  ]
+}

changedInput schema / properties / fields / items / properties / type / enum

Previous value: -[
-  "text",
-  "textarea",
-  "email",
-  "phone",
-  "url",
-  "address",
-  "number",
-  "select",
-  "radio",
-  "checkbox",
-  "ranking",
-  "rating",
-  "scale",
-  "date",
-  "time",
-  "file",
-  "upload",
-  "signature",
-  "appointment",
-  "heading",
-  "page-break",
-  "hidden"
-]New value: +[
+  "text",
+  "textarea",
+  "name",
+  "email",
+  "phone",
+  "url",
+  "address",
+  "number",
+  "select",
+  "radio",
+  "checkbox",
+  "ranking",
+  "rating",
+  "scale",
+  "date",
+  "time",
+  "file",
+  "upload",
+  "signature",
+  "appointment",
+  "heading",
+  "image",
+  "page-break",
+  "hidden"
+]

Changed3 schema fields changedSep 14, 2026

addedInput schema / properties / submitLabel

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 40,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Text on the final button, at most 40 characters. Write what pressing it does, in the form's own voice: \"Book my table\", \"Count me in\", \"Send my RSVP\". Omit for \"Submit\". Ignored on payment forms, whose button always states the amount."
+}

changedInput schema / properties / theme / description

Previous value: -"Visual preset: the form's entire look, not only its background colour.\n\nDESIGNED PRESETS (typography, field styling, depth and background together):\n`editorial`: warm paper, serif title, understated. This is the answer when the user asks for something beautiful, premium, elegant, polished, smart or professional without naming a colour.\n\nCOLOUR PALETTES (background and button colour only, default field styling):\n`default` (warm neutral), `midnight`/`ink` (dark), `royal`/`ocean` (blue), `forest` (green), `sunset` (orange), `rose` (pink), `plum` (purple), `slate` (grey).\n\nHow to choose:\n- They named a colour → that palette.\n- They asked for it to look good but named no colour → `editorial`.\n- They asked for neither → OMIT. A form nobody asked to style stays default.\n\nEach preset is a matched set and cannot be mixed or set piecemeal. If the user asked for something none of these express (a specific hex value, two colours combined, a particular font), apply the nearest and tell them plainly what you could and couldn't do."New value: +"Visual preset: the form's entire look, not only its background colour.\n\nDESIGNED PRESETS (typography, field styling, depth and background together):\n`editorial`: warm paper, serif title, understated. This is the answer when the user asks for something beautiful, premium, elegant, polished, smart or professional without naming a colour.\nCategory presets, each with its own title font; pick by what the form is for:\n`blush`: weddings, engagements, beauty, celebrations.\n`bistro`: restaurants, cafes, catering, food orders, hotels.\n`playground`: schools, courses, kids' classes, summer camps.\n`studio`: gyms, fitness classes, sport, races (dark).\n`clinic`: healthcare, dental, therapy, patient intake.\n`noir`: tattoo, photography, music, creative studios (dark).\nThese show a cover photo behind the title when the form has one.\n\nCOLOUR PALETTES (background and button colour only, default field styling):\n`default` (warm neutral), `midnight`/`ink` (dark), `royal`/`ocean` (blue), `forest` (green), `sunset` (orange), `rose` (pink), `plum` (purple), `slate` (grey).\n\nHow to choose:\n- They named a colour → that palette.\n- The form clearly belongs to one of the categories above → that category preset.\n- They asked for it to look good but named no colour → `editorial`.\n- They asked for neither → OMIT. A form nobody asked to style stays default.\n\nEach preset is a matched set and cannot be mixed or set piecemeal. If the user asked for something none of these express (a specific hex value, two colours combined, a particular font), apply the nearest and tell them plainly what you could and couldn't do."

changedInput schema / properties / theme / enum

Previous value: -[
-  "default",
-  "midnight",
-  "royal",
-  "forest",
-  "ocean",
-  "sunset",
-  "rose",
-  "plum",
-  "slate",
-  "ink",
-  "editorial"
-]New value: +[
+  "default",
+  "midnight",
+  "royal",
+  "forest",
+  "ocean",
+  "sunset",
+  "rose",
+  "plum",
+  "slate",
+  "ink",
+  "editorial",
+  "blush",
+  "bistro",
+  "playground",
+  "studio",
+  "clinic",
+  "noir"
+]

First observedSep 10, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description adds one genuinely new behavioral fact — that a successful create yields a public link, i.e. the created object is externally shareable — but says nothing about permissions, reversibility, or cleanup of the public link, so it only partially extends the annotations.

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?

Three short sentences, front-loaded with the action and its result, then the disambiguation rule. Every sentence earns its place and nothing is repeated from the schema or annotations.

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 shape need not be described, and the schema documents the nine parameters thoroughly. The description covers creation semantics and the sibling overlap, though it omits any note on what happens on a failed create or how the returned link relates to publish/invitation flows.

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 high (78%) and the schema itself carries unusually rich parameter guidance (theme presets, field types, upload vs file, templateSlug semantics, notAnInvitation), so the baseline is 3. The description contributes no parameter-level detail of its own; it spends its text on object disambiguation instead.

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 ('Create a new form'), names the return artifact (public link), and explicitly differentiates from the sibling create_invitation by warning that 'wedding invitation form' usually means the invitation page rather than a questionnaire. An agent can disambiguate without opening either schema.

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 a clear when-not-to-use rule with the alternative named (create_invitation), which is the highest-risk confusion for this tool. It does not, however, cover the other selection choices an agent faces on this tool, such as templateSlug vs hand-written fields or when a plain questionnaire is appropriate versus an invitation.

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

All Deoochform 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.

Create form

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources