Skip to main content
Glama

furrow-forms

by com.furrowforms

Update form

update_form
Idempotent

Use to patch form overrides. Pass null on an override to inherit again. Set email.subject or email.intro to override project notification copy for this form only; from_name, footer_mode, and include_meta stay on the project. Email templates support {{project.name}}, {{project.slug}}, {{form.name}}, {{form.slug}}, {{count}} (1-based clean submissions on this form, including the current one), and any submission field such as {{name}} or {{email}}. Use a fallback with {{name | "New submission"}}. Missing fields render empty and never error. Do not pass HTML; Furrow renders one owned layout. Set webhook_url_override to override the project webhook for this form. Do not use this to change Turnstile keys — those live on the project. Checkbox groups, select multiple, and other multi-value HTML fields must use a [] suffix on the name (name="services[]") or only the last checked value is stored. Put services[] on field_contract.name too. JSON/fetch should send a real array without brackets ({ "services": ["a", "b"] }) and must not use Object.fromEntries(formData) — use formData.getAll("services"). Single checkbox, select, or combobox: no brackets. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew form display name.
emailNoPer-form subject and intro overrides for the notification email.
form_idYesForm id from list_forms, create_form, or bootstrap_site.
field_contractNoDeclared fields (name, type, label, report). Drives get_snippet and the email layout. Null clears it.
webhook_url_overrideNoWebhook endpoint for this form only. Null inherits the project webhook.
redirect_url_overrideNoSuccess redirect for this form only. Null inherits default_redirect_url.
notify_emails_overrideNoRecipients for this form only. Null inherits the project's notify_emails.
webhook_secret_overrideNoHMAC secret for this form's webhook. Null inherits the project secret.
require_turnstile_overrideNoForce Turnstile on or off for this form. Null inherits the project setting.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

The description discloses many behavioral details beyond annotations: null overrides re-inherit project values, missing template fields render empty and never error, checkbox groups require [] suffixes or only the last value is stored, and file downloads live under a form-slug folder at files_url. These details align with idempotentHint=true and readOnlyHint=false, so no contradiction exists.

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?

The description is long but every sentence carries operational value, and the purpose statement is front-loaded before the caveats. It avoids restating schema metadata and packs only the failure-prone details (HTML vs JSON array encoding, multipart uploads, template fallbacks) into a dense but non-redundant block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter nested-object tool with no output schema, the description covers the critical semantic ground: override inheritance, token interpolation, multi-value field encoding, upload prerequisites, and public URL cautions. The remaining parameter details are all present in the 100%-covered schema, so an agent has everything needed to call update_form correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is already 100%, the description adds significant meaning: email token syntax with {{project.name}} and {{count}}, fallback syntax {{name | "New submission"}}, webhook_url_override behavior, field_contract.name [] rules, and JSON vs formData distinction. This is precisely the kind of value beyond the schema that helps an agent pick correct parameter values.

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?

The description opens with a specific verb and resource: 'Use to patch form overrides,' which immediately distinguishes it from broader project tools like update_project. It further clarifies scope by stating what stays on the project (from_name, footer_mode, include_meta) and explicitly excludes Turnstile key changes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('patch form overrides'), alternative routing ('Do not use this to change Turnstile keys — those live on the project'), and prerequisites ('Enable uploads on the project first'). The from_name/footer_mode/include_meta note signals when update_project is the right sibling instead.

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

All furrow-forms toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools are clearly separated by resource and action (get_client vs list_clients vs create_client), and the descriptions explicitly warn against misuse. However, update_account and update_team both cover renaming a workspace/team, and get_account and get_project both return plan/usage/branding, creating a couple of genuinely confusing boundaries.

Naming Consistency4/5

The set overwhelmingly follows the snake_case verb_noun pattern: archive_client, create_form, get_submission, list_projects, rotate_project_inbox, test_webhook, etc. Minor deviations exist: bootstrap_site uses 'site' instead of 'project', update_team vs update_account introduces noun inconsistency, and upsert_project_webhook uses a different verb than the update_* family.

Tool Count2/5

With 27 tools, the server exceeds the 25-tool threshold that signals a too-large surface for an MCP server. While the broad scope (clients, projects, forms, submissions, teams, billing, webhooks) explains the count, there are redundant near-duplicates like update_account/update_team and bootstrap_site overlapping with multiple create tools, making the set feel bloated rather than curated.

Completeness3/5

The lifecycle coverage for clients, projects, and forms is solid with create, read, list, update, and archive operations. However, there is no unarchive (explicitly noted as unavailable), no submission management beyond read (no delete/export/update), and no webhook delivery history, leaving notable dead ends and gaps in the core workflow.

Resources