Skip to main content
Glama

Finalize workspace setup

finalize_workspace_setup
DestructiveIdempotent

Commit onboarding answers into the workspace config; omitted fields stay untouched. active_motions records the confirmed motion choice and applies each motion's template; feature_templates applies standalone add-on templates (opted into during the interview) after the motion templates — an unknown feature key is skipped and named, 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finalize_workspace_setup"
  }
}

Input 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 (which stages exist and their labels). An existing key keeps its role and entry requirements; 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_motionsNoGuard 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). If the saved motions differ, nothing is saved and the result returns updated:false with the current motions.

Output Schema

NameRequiredDescriptionDefault
updatedNo
guidanceNo
workspaceNoThe workspace's state — the same shape start_onboarding returns as `state`.
workspace_urlNo
active_motionsNo
import_evidenceNo
applied_templateNo
applied_templatesNo
skipped_feature_templatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / import_evidence
      Added value: +{
      +  "properties": {},
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed9 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / applied_template / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / applied_template / properties / applied / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / applied_templates / items / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / applied_templates / items / properties / applied / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / workspace / additionalProperties
      Removed value: -{}
    • addedOutput schema / properties / workspace / description
      Added value: +"The workspace's state — the same shape start_onboarding returns as `state`."
    • removedOutput schema / properties / workspace / properties
      Removed value: -{
      -  "framework": {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "null"
      -      }
      -    ]
      -  },
      -  "id": {
      -    "format": "uuid",
      -    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      -    "type": "string"
      -  },
      -  "name": {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "null"
      -      }
      -    ]
      -  },
      -  "pipeline_stages": {
      -    "items": {},
      -    "type": "array"
      -  }
      -}
  4. Changed2 schema fields changed
    • changedInput schema / properties / expected_active_motions / description
      Previous value: -"Optional 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."New value: +"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). If the saved motions differ, nothing is saved and the result returns updated:false with the current motions."
    • changedInput schema / properties / pipeline_stages / description
      Previous value: -"The 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."New value: +"The default pipeline's stages, in order (which stages exist and their labels). An existing key keeps its role and entry requirements; an omitted is_closed / is_won keeps its stored value unless the flag you do send contradicts it."
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds substantial context on top: omitted fields stay untouched (merge, not replace), unknown feature keys are skipped and named rather than failing, an unknown template_key is refused, and expected_active_motions acts as an optimistic-concurrency guard returning updated:false. These are non-obvious behavioral traits an agent could not infer from the annotations.

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?

Front-loaded with the core action, then a usage block and an example; each section is purposeful. It runs long and repeats the feature_templates skip/refuse semantics in both the body and the parameter list, which is minor waste but not confusing.

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?

For a 9-parameter, nested-object mutation tool with an output schema and full annotations, the description covers merge semantics, template application order, failure-vs-skip behavior, and the concurrency guard. Return shape is delegated to the output schema, which is acceptable; only explicit guidance on defaults when everything is omitted is slightly thin.

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, but the description genuinely adds meaning the schema does not: feature_templates are applied AFTER motion templates, active_motions each triggers its matching template, answers are merged into stored onboarding answers, and expected_active_motions is explained as a read-then-write guard. The only redundancy is repeating the feature_templates skip behavior already stated in its schema description.

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?

States a specific verb and resource: 'Commit onboarding answers into the workspace config', then enumerates exactly which payload fields do what (active_motions applies motion templates, feature_templates applies add-ons, answers fills checklist gaps). This distinguishes it cleanly from update_workspace and start_onboarding, which the description references by name.

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?

The 'When to use' block gives a concrete trigger — end of the interview, after the user has confirmed the choices — plus an example user utterance. It does not explicitly say when NOT to use it versus siblings like update_workspace or show_workspace_setup, which is the only missing piece.

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