Skip to main content
Glama

furrow-forms

by com.furrowforms
OverviewDiscussionsAdmin

Update account

update_account
Idempotent

Use to rename the workspace, set branding, or configure the AI spam filter. 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 when Jev flags a submission; no webhook is sent either way. Heuristic spam stays silent. Free accounts cannot set branding.mode or email.footer_mode to anything but furrow — those writes are ignored. 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. 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

TableJSON Schema
NameRequiredDescriptionDefault
aiNoAI spam filter. Off until this team saves its own TypeSafe key. One Jev call per heuristics-clean submission.
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 / 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"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations (readOnlyHint=false, idempotentHint=true) indicate mutation and idempotency, and the description amplifies this with critical behavioral details: writes to branding.mode on free accounts are silently ignored, the TypeSafe key is write-only and never returned, and notify_suspected_spam controls email/webhook behavior. It also discloses how plan tiers affect accepted values and how token scoping changes team_id requirements. This is far more than the annotations provide.

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

Conciseness4/5

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

The description is long but every sentence carries substantive information about behavior, plan restrictions, or routing. It is front-loaded with the core purpose and then logically expands into parameter nuances, plan gates, and alternatives. There is some redundancy with the schema, but overall it uses its length to communicate important restrictions that would otherwise be invisible to an agent.

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?

The description covers the tool's purpose, when to use it versus alternatives, parameter behavior including plan-driven constraints, token scoping rules, and the fact that some writes are silently ignored. With no output schema, it conveys the essential operational context an agent needs to invoke this safely and correctly. No critical information appears 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?

The schema already documents all 4 parameters at 100% coverage, so the baseline is 3. The description adds valuable semantics beyond the schema: null clears the key, writes on free plans for branding.mode are ignored, notify_suspected_spam defaults to true, and team_id is required only for operator tokens. This goes beyond simple property definitions, though some details (e.g., maxLength) naturally remain in the schema.

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 clear verb and resource: "Use to rename the workspace, set branding, or configure the AI spam filter." It names the three concrete operations, making it immediately distinguishable from sibling tools like create_upgrade_link or update_team. The specificity leaves no ambiguity about which tool an agent should select.

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?

Explicit routing is provided: "Do not use this to change the plan — call create_upgrade_link." It also names the alternative for plan changes and describes when to use create_upgrade_link (Stripe Checkout / Customer Portal). The description clearly states prerequisites around billing tiers and token scoping, so an agent knows exactly when this tool applies.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources