Skip to main content
Glama

Start Company Formation

start_formation

Starts the user's LLC or C-Corp formation: saves their legal name (only when the profile lacks it), their country of residence, the company name, and the formation state and entity type. Every field is optional and is saved as given, so call it as soon as you have an answer. state and entityType default to a Wyoming LLC, so call it with {} when the user has no preference. Never invent a company name. Formation flow, in order: start_formation, create_checkout_session, verify_payment, save_company_details (industries from search_industries), submit_formation. Each response's nextStep is the step the flow now waits on.

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_formation"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter code of the US state to form in, as the user chose. Wyoming (WY) when they have no preference.
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.
lastNameNoLegal last name as on the user's ID. Only needed when the profile lacks it; send with firstName.
firstNameNoLegal first name as on the user's ID. Only needed when the profile lacks it; send with lastName.
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.
entityTypeNoLLC or CCorp, as the user chose. LLC when they have no preference.
companyNameNoThe company name the user chose, without the LLC or Inc. suffix. Never invent or suggest one.
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.
countryOfResidenceNoCountry the user personally lives in, ISO 3166-1 alpha-3 (e.g. USA, GBR, BRA).

Output Schema

NameRequiredDescriptionDefault
codeNoStructured error code when error=true (e.g. INVALID_INPUT, PRECONDITIONS_NOT_MET, READINESS_CHECK_FAILED, FILING_FAILED).
errorNotrue if the call failed
savedNoWhat this call saved.
messageNoHuman-readable status.
missingNoPrerequisites still unmet, in flow order. Empty when only filing remains.
nextStepNoThe step the formation flow now waits on; null once formation is complete.
companyIdNoThe company the call acted on.
companyNameNoName of the company the call acted on. Name it to the user.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / message / description
      Previous value: -"Human-readable status or instruction."New value: +"Human-readable status."
    • 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."
    • changedOutput schema / properties / nextStep / description
      Previous value: -"The tool to call next; null when the flow is complete."New value: +"The step the formation flow now waits on; null once formation is complete."
    • addedOutput schema / properties / nextStep / properties
      Added value: +{
      +  "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"
      +  }
      +}
    • changedOutput schema / properties / nextStep / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "object",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / companyName / description
      Previous value: -"The company name the user chose, without the LLC suffix. Never invent or suggest one."New value: +"The company name the user chose, without the LLC or Inc. suffix. Never invent or suggest one."
    • addedInput schema / properties / entityType
      Added value: +{
      +  "description": "LLC or CCorp, as the user chose. LLC when they have no preference.",
      +  "enum": [
      +    "LLC",
      +    "CCorp"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Two-letter code of the US state to form in, as the user chose. Wyoming (WY) when they have no preference.",
      +  "enum": [
      +    "AK",
      +    "AL",
      +    "AR",
      +    "AZ",
      +    "CA",
      +    "CO",
      +    "CT",
      +    "DC",
      +    "DE",
      +    "FL",
      +    "GA",
      +    "HI",
      +    "IA",
      +    "ID",
      +    "IL",
      +    "IN",
      +    "KS",
      +    "KY",
      +    "LA",
      +    "MA",
      +    "MD",
      +    "ME",
      +    "MI",
      +    "MN",
      +    "MO",
      +    "MS",
      +    "MT",
      +    "NC",
      +    "ND",
      +    "NE",
      +    "NH",
      +    "NJ",
      +    "NM",
      +    "NV",
      +    "NY",
      +    "OH",
      +    "OK",
      +    "OR",
      +    "PA",
      +    "RI",
      +    "SC",
      +    "SD",
      +    "TN",
      +    "TX",
      +    "UT",
      +    "VA",
      +    "VT",
      +    "WA",
      +    "WI",
      +    "WV",
      +    "WY"
      +  ],
      +  "type": "string"
      +}
  3. 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"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false, so the description carries real weight and delivers: every field is optional, values are saved as given, and state/entityType fall back to a Wyoming LLC. It also notes the legal name is only written when the profile lacks it and that each response's nextStep indicates the waiting step. The notable gap is re-invocation behavior — nothing says whether calling twice creates a second formation or overwrites the first.

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?

Three dense sentences, front-loaded with the action and its side effects before the flow ordering and defaults. Every sentence carries information, though the field enumeration in the first sentence partially duplicates the schema descriptions and could be trimmed.

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 nine-parameter tool with an output schema, the description covers the essentials: defaults, optionality, saving semantics, ordering of the flow, and where to get industries. What is missing is idempotency/duplicate-call behavior and any distinction from start_new_company, both of which an agent would need before calling it in a resumed session.

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, including the enums and the analytics-only fields. The description adds a little beyond it — that omitting state/entityType yields a Wyoming LLC and that the company name excludes the LLC/Inc. suffix — but most of its parameter content restates the schema, so the baseline of 3 applies.

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 — starts an LLC or C-Corp formation — and enumerates exactly what it persists (legal name, country of residence, company name, state, entity type). It is easy to distinguish from downstream steps like create_checkout_session or submit_formation, but it never explains how it differs from the sibling start_new_company, which reads like the same action.

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 when-to-use guidance: 'call it as soon as you have an answer', 'call it with {} when the user has no preference', and 'Never invent a company name'. It also supplies the ordered flow (start_formation → create_checkout_session → verify_payment → save_company_details → submit_formation) and points to search_industries for the industries input, so the agent knows both timing and the adjacent alternatives.

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.