MCP server for managing Jotform forms, submissions, and AI-powered form generation
Server has 8 tools with explicit schemas and descriptions. All tools are properly registered with mcpgo.NewTool() and include descriptions (10-100 chars). Input schemas are present for all tools with proper type definitions (string, number). However, descriptions are uniformly brief (10-100 chars, well below the 194-char baseline for A+ tools), lacking context on WHEN to use each tool, prerequisites, or recovery guidance. Parameter descriptions are minimal. Output schemas are not documented, LLMs cannot predict response structure. Error handling is present but generic. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Missing pagination guidance for list_submissions despite accepting a limit parameter.
Create a new Jotform form from a JSON schema
Delete a Jotform form permanently
Export a Jotform form structure as formatted JSON for version control
Generate a Jotform form schema from a natural language description using AI
Get the full structure (questions, properties) of a Jotform form
List all Jotform forms for the authenticated account
Output schemas not documented. LLMs cannot predict response structure, forcing them to guess what fields are returned and how to chain tools. Affects all 8 tools.
Descriptions are uniformly brief (10-100 chars, avg ~50 chars vs 194-char baseline). Lack context on WHEN to use each tool, prerequisites, or what distinguishes similar tools (e.g., export_form vs get_form). LLMs cannot determine tool selection intent.
No tool annotations despite clear risk levels. delete_form is DESTRUCTIVE but lacks destructiveHint. create_form and update_form are WRITE but lack idempotentHint guidance. list_* tools are READ_ONLY but lack readOnlyHint. Agents cannot reason about retry safety.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
Retrieve recent submissions for a Jotform form
Update an existing Jotform form with a new JSON schema
Parameter descriptions are minimal or missing context. 'form_id' appears in 6 tools but descriptions do not explain format (numeric string? integer?), range, or how to obtain one. 'schema' parameter in create_form and update_form lacks guidance on valid JSON structure or examples.
list_submissions accepts 'limit' parameter but no pagination guidance (no offset, cursor, or total_count return documented). Large result sets risk context window exhaustion. No documented cap on default or max results.