Skip to main content
Glama

Finalize workspace setup

finalize_workspace_setup
DestructiveIdempotent

Commit onboarding answers into the workspace config. Any field omitted is left untouched. active_motions records the confirmed motion choice and auto-applies each chosen motion's template; feature_templates applies additional standalone add-on templates (opted into during the interview) AFTER the motion templates — an unknown feature key is skipped and named in the result, never a failure; answers records checklist items without a dedicated field. Returns the updated workspace.

When to use: Call at the end of the interview once the user has confirmed the choices. Records the confirmed motion(s), applies their starter templates, and commits the answers — anything omitted keeps its default.

Example: Looks good — save those settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe workspace's display name — answers the checklist's name item; until set it reads "<sign-up email domain> workspace".
answersNoAnswers to checklist items with no dedicated field, keyed by the checklist key (e.g. quoting_catalog); merged into the saved onboarding answers.
frameworkNoQualification framework whose fields are filled on opportunities; passing the current default (spiced) records it as a chosen answer.
template_keyNoKey of one extra starter template to apply beyond the chosen motions, from start_onboarding's available_templates; an unknown key is refused.
active_motionsNoThe confirmed motion key(s) from start_onboarding's available_motions — saved as the workspace's active motions, each applying its matching template.
pipeline_stagesNoThe default pipeline's stages, in order: the list sets which stages exist and their labels. A stage whose key already exists keeps its role and entry requirements, and an omitted is_closed / is_won keeps its stored value unless the flag you do send contradicts it.
framework_customNoCustom framework definition for framework 'custom', shaped {fields:[{key,label}]} — each key becomes a qualification field on opportunities.
feature_templatesNoKeys of standalone add-on templates opted into during the interview (e.g. quoting), applied after the motion templates; unknown keys are skipped and named, never refused.
expected_active_motionsNoOptional guard against saving over a newer choice: the active_motions you last read (state.active_motions from start_onboarding or show_workspace_setup; null when none was confirmed). If the saved motions no longer match, nothing is saved and the result returns updated:false with the current motions and workspace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatedNo
guidanceNo
workspaceNo
workspace_urlNo
active_motionsNo
applied_templateNo
applied_templatesNo
skipped_feature_templatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing merge semantics ('any field omitted is left untouched'), the distinct failure modes (unknown feature key skipped and named vs. template key refused), and the expected_active_motions guard returning updated:false. This is meaningful behavioral context for a destructive, non-read-only operation.

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?

The core purpose is front-loaded, but the 'When to use' paragraph repeats the first paragraph's omission rule ('anything omitted keeps its default' vs 'any field omitted is left untouched'), and the example line is thin. Some redundancy blunts the structure.

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

Completeness4/5

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

Given nine parameters, nested objects, and an output schema, the description covers the key semantics (omission behavior, template ordering, guard) and need not explain return values. The trigger context is present, though the destructive/overwrite implications for pipeline_stages could be spelled out more.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all nine parameters. The description's notes on active_motions, feature_templates ordering, and unknown-key handling largely restate the schema descriptions, adding only marginal value. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Commit onboarding answers into the workspace config,' which is more specific than a generic update. It reads as the onboarding-finalization step rather than a general workspace update, though it never explicitly contrasts with the update_workspace sibling.

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

Usage Guidelines4/5

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

Provides a clear trigger condition: 'Call at the end of the interview once the user has confirmed the choices.' However, it names no alternatives or exclusions (e.g., when to use update_workspace instead), so the when-not-to-use side is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources