Skip to main content
Glama

furrow-forms

by com.furrowforms

Update team

update_team
Idempotent

Use to rename a team. 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 create another workspace — that is dashboard-only and requires yearly. For plan, usage, retention, and branding, call get_account / update_account. Do not use this to change clients or projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNew team (workspace) display name.
team_idNoTeam id from list_teams. Required for operator tokens and OAuth logins; team-scoped frw_ tokens may omit it.

Schema Changelog

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

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations only indicate readOnly=false and idempotentHint=true. The description adds meaningful behavioral context about authentication scoping: operator tokens must pass team_id, while team-scoped tokens may omit it and cannot target another workspace. This goes beyond what the annotations convey.

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 compact and front-loaded with the primary purpose, then delivers token constraints and exclusions in efficient sentences. Every sentence adds necessary guidance; there is no filler or redundancy.

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 two-parameter mutation tool with no output schema, the description is complete enough for correct selection and invocation. It covers the action, token behavior, required parameter provenance, and explicitly rules out adjacent use cases.

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 adds extra semantics for team_id by clarifying operator-token requirements and the 'cannot target another workspace' restriction for team-scoped tokens, which is not fully captured 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 specific verb and resource: 'Use to rename a team.' It then explicitly distinguishes itself from creating a workspace, changing account-level settings, and changing clients/projects, so an agent can differentiate it from siblings like update_account, update_client, and update_project.

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?

The description gives explicit when-to-use and when-not-to-use guidance. It names get_account/update_account as the correct tools for plan, usage, retention, and branding, and warns against using this tool to create workspaces or change clients/projects. It also explains token-specific requirements for team_id.

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