Skip to main content
Glama

Start a New Company

start_new_company

Begin a brand-new company formation alongside any existing companies the customer already has — call when the customer explicitly asks to form a SECOND (or further) company. Creates an empty in-progress Company row, links it to the customer, and pins it as the active company so the next tool calls operate on it. The response's nextStep is the new company's first formation step. The previously active company is untouched and remains in list_companies, and switch_active_company makes it active again.

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": "start_new_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Output Schema

NameRequiredDescriptionDefault
errorNotrue if an error occurred
messageNoError message if error=true
nextStepNoThe step the formation flow now waits on; null once formation is complete.
companyIdNoKSUID of the newly-created company, now the active company
nextQuestionNoThe customer-facing question for nextStep; null once formation is complete.
conversation_idNoThis conversation's handle. Pass it unchanged as conversation_id on every later call.
suggestedNextStepNoThe tool for the new company's first formation step

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / nextAction
      Removed value: -{
      -  "description": "Imperative for the agent — follow verbatim.",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / nextActionInput
      Removed value: -{
      -  "description": "{tool, arguments} template for the next call. Replace every <placeholder> in arguments with the user's real answer.",
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • changedOutput schema / properties / nextQuestion / description
      Previous value: -"Question to ask the user verbatim before the next call."New value: +"The customer-facing question for nextStep; null once formation is complete."
    • addedOutput schema / properties / nextStep
      Added value: +{
      +  "description": "The step the formation flow now waits on; null once formation is complete.",
      +  "properties": {
      +    "description": {
      +      "description": "Where the customer stands at this step and what their options are.",
      +      "type": "string"
      +    },
      +    "missingFields": {
      +      "description": "Arguments of that tool the step still needs.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "tool": {
      +      "description": "The tool that records this step.",
      +      "type": "string"
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "This conversation's handle. Pass it unchanged as conversation_id on every later call.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world call; the description goes well beyond that by disclosing the row-creation semantics, the customer linkage, the active-company pinning for subsequent calls, and that nextStep carries the first formation step. It also states a non-obvious safety property: the previously active company is left intact and recoverable.

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?

Front-loaded with the trigger condition and scope, then the concrete effect, then the return hint, then the reversibility guarantee — four tight sentences with no filler. Every clause (second-company qualifier, active pinning, nextStep, old company preserved) carries information the agent needs to act correctly.

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 zero-required-parameter mutation with an output schema, the definition covers trigger, side effects, follow-up call guidance, and the undo path via `switch_active_company`. Nothing an agent needs to invoke it safely or interpret the result is missing.

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?

All three parameters are optional analytics fields already fully documented in the schema (100% coverage), so the description adds nothing about them. Baseline 3 applies when the schema does all the work and there is nothing semantic left for the description to clarify.

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 ("Begin a brand-new company formation") and immediately narrows the scope to forming a SECOND or further company, which cleanly separates it from create/start_formation and the other siblings. It also names the concrete side effect — an empty in-progress Company row linked to the customer — so the agent knows exactly what object is produced.

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?

Gives an explicit trigger condition ("call when the customer explicitly asks to form a SECOND (or further) company") and implicitly excludes first-time formation. It also routes the alternate intent away by naming `list_companies` for the old company and `switch_active_company` to reactivate it, so the agent can choose between the three without inspecting schemas.

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.