Tally MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_formA | Create a new Tally form with specified fields and configuration. This tool converts simple field definitions into Tally's complex blocks-based structure automatically. The status field is optional and defaults to DRAFT if not specified. |
| modify_formC | Modify an existing Tally form |
| get_formC | Retrieve details of a specific Tally form |
| list_formsB | List all forms in the workspace |
| delete_formA | Delete a Tally form |
| preview_bulk_deleteA | SAFETY PREVIEW: Show exactly which forms would be deleted before bulk deletion. MANDATORY: Present form details to human and require explicit "DELETE ALL" confirmation before proceeding to confirm_bulk_delete. |
| confirm_bulk_deleteA | HUMAN CONFIRMATION: Confirm bulk deletion ONLY after human responds with exact phrase "DELETE ALL". DO NOT call this automatically - requires genuine human confirmation. |
| bulk_delete_formsA | đźš« DEPRECATED: Use confirm_bulk_delete instead. This tool now requires human confirmation via the confirm_bulk_delete tool after preview_bulk_delete. The new workflow is: 1) preview_bulk_delete, 2) confirm_bulk_delete with user choice, 3) automatic execution. This tool is kept for backward compatibility but will reject calls without proper confirmation workflow. |
| get_submissionsC | Retrieve submissions for a specific form |
| analyze_submissionsC | Analyze form submissions and provide insights |
| share_formC | Generate sharing links and embed codes for a form |
| manage_workspaceC | Manage workspace settings and information |
| manage_teamC | Manage team members and permissions |
| delete_formA | DEPRECATED: Use preview_single_delete and confirm_single_delete for secure deletion |
| preview_single_deleteA | Preview a single form before deletion. MANDATORY: Present form details to human and require explicit "DELETE" confirmation before proceeding to confirm_single_delete. |
| confirm_single_deleteA | Confirm single form deletion ONLY after human responds with exact phrase "DELETE". DO NOT call this automatically - requires genuine human confirmation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tally_form_sharing_guide | Guide for choosing the correct share type when sharing Tally forms |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
The tool set has clear distinct purposes for core operations like create_form, get_form, list_forms, and manage_team, but there is significant overlap and confusion around deletion tools. The deprecated delete_form, bulk_delete_forms, and their preview/confirm counterparts create ambiguity, as agents might misselect between deprecated and active tools or misunderstand the multi-step workflow required for deletions.
Most tools follow a consistent verb_noun pattern (e.g., create_form, get_form, list_forms), which aids readability. However, there are minor deviations such as analyze_submissions (verb_noun) versus manage_team (verb_noun) and manage_workspace (verb_noun), which are consistent internally but slightly less so with others. The naming is generally predictable with only small inconsistencies.
With 15 tools, the count is reasonable for managing Tally forms, submissions, and workspace settings, covering a broad scope. It is slightly high due to redundant deletion tools (deprecated and new workflow), but overall, it aligns well with the server's purpose without being overwhelming.
The tool set provides comprehensive coverage for Tally form management, including CRUD operations (create_form, get_form, modify_form, deletion workflow), submission handling (get_submissions, analyze_submissions), workspace and team management (manage_workspace, manage_team), and sharing (share_form). There are no obvious gaps; the deprecated tools are noted but replaced with a secure workflow, ensuring agents can handle all essential tasks.