get_formGet a form's full definition.
| Name | Required | Description | Default |
|---|---|---|---|
| formId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| rules | Yes | ||
| theme | Yes | ||
| title | Yes | ||
| fields | Yes | ||
| formId | Yes | ||
| status | Yes | ||
| createdAt | Yes | ||
| publicUrl | Yes | ||
| updatedAt | Yes | ||
| description | No |
Changes observed during successful MCP inspections.
Output schema / properties / fields / items / properties / formulaAdded value: +{
+ "maxLength": 500,
+ "type": "string"
+}Output schema / properties / fields / items / properties / type / descriptionPrevious 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."Output schema / properties / fields / items / properties / type / enumPrevious 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"
+]Output schema / properties / fields / items / properties / imageUrlAdded value: +{
+ "anyOf": [
+ {
+ "format": "uri",
+ "type": "string"
+ },
+ {
+ "pattern": "^\\/templates\\/(?:[a-z0-9-]+\\.svg|photos\\/[a-z0-9-]+\\.jpg)$",
+ "type": "string"
+ }
+ ]
+}Output schema / properties / fields / items / properties / type / enumPrevious 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"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description only needs to add context beyond that. It adds 'full definition' as a scoping detail, but offers no further behavioral information such as error handling, 404 behavior, or authentication needs. With annotations present, this is adequate but not enriched.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single five-word sentence that is front-loaded with the core action and resource. There is zero filler or repetition; every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read operation with a present output schema and safety annotations, the definition is nearly complete. The only notable gap is the lack of a pointer to list_forms for discovering valid IDs, but the sibling list makes that easy to infer. Overall, an agent can correctly call this tool with the information provided.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for formId. The phrase 'a form's full definition' implies that formId identifies the target form, which is helpful. However, it does not explicitly define the parameter, its expected format, or how to obtain a valid ID. The parameter is self-explanatory, but the description adds minimal semantic value beyond the name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get'), a clear resource ('form'), and a scope qualifier ('full definition'). This cleanly separates it from siblings like list_forms (which lists forms, presumably as summaries) and get_submission (a different resource). The meaning is immediately unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use case is implied by the name and description: fetch a single form's complete definition by ID. However, the description provides no explicit guidance on when to choose this over list_forms or get_submission, nor does it point to list_forms for discovering valid form IDs. Usage guidance is inferred, not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.