Skip to main content
Glama

furrow-forms

by com.furrowforms
OverviewDiscussionsAdmin

Update account

update_account
Idempotent

Use to rename the workspace, set branding, configure the AI spam filter, or connect the team's own Twilio account for new-lead text alerts. Pass sms { account_sid, auth_token, from } to save Twilio (auth_token is write-only; omit it later to keep the saved one; sms: null disconnects). Numbers to text are notify_phones on the project. US senders must finish A2P 10DLC or toll-free verification in Twilio or carriers drop the texts. To set it up with a human who has never used Twilio, follow furrow://docs/text-alerts. Pass ai.typesafe_api_key to save this team's TypeSafe key (null clears it; the key is write-only). ai.notify_suspected_spam (default true) emails notify addresses with a Potential spam label for every spam catch — rule-based or Jev — except exact duplicates; set it false to silence both. Spam never sends a webhook. Free accounts keep branding.mode and email.footer_mode at furrow; asking for anything else returns plan_limit — tell the human the custom footer is a Yearly feature and offer create_upgrade_link. Yearly may set branding.mode to furrow, off, or agency (name + optional link + optional logo; Furrow keeps the layout, no raw HTML). Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. Operator tokens (all workspaces) must pass team_id from list_teams. Team-scoped tokens may omit team_id and cannot target another workspace. Do not use this to change the plan — call create_upgrade_link.

Input Schema

NameRequiredDescriptionDefault
aiNoAI spam filter. Off until this team saves its own TypeSafe key. One Jev call per heuristics-clean submission.
smsNoThe team's own Twilio account for new-lead text alerts. Null removes it. Numbers to text live on the project (notify_phones).
nameNoNew workspace display name.
team_idNoTeam id from list_teams. Required for operator tokens and OAuth logins; team-scoped frw_ tokens may omit it.
brandingNoAccount-wide branding for notification emails and hosted pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sms
      Added value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "account_sid": {
+          "description": "Twilio Account SID (AC…).",
+          "pattern": "^AC[0-9a-fA-F]{32}$",
+          "type": "string"
+        },
+        "auth_token": {
+          "description": "Twilio Auth Token. Write-only, stored encrypted, never returned. Required the first time; omit later to keep the saved one.",
+          "maxLength": 200,
+          "minLength": 1,
+          "type": "string"
+        },
+        "from": {
+          "description": "Sending Twilio number in E.164, or a Messaging Service SID (MG…). US senders need A2P 10DLC or toll-free verification done in Twilio first.",
+          "maxLength": 64,
+          "type": "string"
+        },
+        "provider": {
+          "default": "twilio",
+          "description": "SMS provider. Only twilio today.",
+          "enum": [
+            "twilio"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "account_sid",
+        "from"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The team's own Twilio account for new-lead text alerts. Null removes it. Numbers to text live on the project (notify_phones)."
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / ai
      Added value: +{
+  "description": "AI spam filter. Off until this team saves its own TypeSafe key. One Jev call per heuristics-clean submission.",
+  "properties": {
+    "notify_suspected_spam": {
+      "description": "When true (the default), submissions the AI flags as spam still email notify addresses with a Potential spam label and send no webhook. Set false to silence those emails.",
+      "type": "boolean"
+    },
+    "typesafe_api_key": {
+      "anyOf": [
+        {
+          "maxLength": 500,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "TypeSafe API key for the AI spam filter. Send null or an empty string to remove it. The key is write-only and never returned."
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond readOnlyHint=false/idempotentHint=true: discloses that free plans return plan_limit for non-furrow branding, that spam never fires a webhook, that secrets are write-only, and that sms: null disconnects. Loses a point because the plan/capacity paragraph is padded and partially restates the branding constraint already stated earlier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with concrete actions, which is good, but the plan-limit rule appears twice (once as 'Free accounts keep branding.mode and email.footer_mode at furrow' and again in the Free/Yearly tier breakdown), and the pricing paragraph is longer than the calling agent needs.

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 5-parameter mutation tool with nested objects and no output schema, the description covers error paths (plan_limit), permission/token scoping, null semantics for every nested field, and where the plan lives instead. Nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds operational meaning — omit auth_token later to keep the saved one, null clears the TypeSafe key, notify_suspected_spam defaults true and affects both email and webhooks, and notify_phones live on the project not here.

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?

Opens with a specific verb and enumerates the exact resources it changes: workspace name, branding, AI spam filter, Twilio SMS. An agent can distinguish it from update_team and update_project without opening any schema.

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?

Explicitly routes away from itself: 'Do not use this to change the plan — call create_upgrade_link,' and names list_teams as the source of team_id for operator tokens. It also names the escalation path (furrow://docs/text-alerts, create_upgrade_link) for the human-facing cases.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources