Lovie Company Formation

Start Formation

formation_start_formation

THE entry point for a new company formation — runs anonymously, no sign-in required. Call this DIRECTLY whenever the user wants to start, create, or form a company or formation. Do NOT call company_get_my_companies or formation_get_list_formations first; those require auth and are only for existing records — starting a new formation needs neither. Returns a formation_id plus the ordered steps. Calling it again for the same signed-in user RESUMES the formation already in progress and returns its id with resumed=true — it does not create a second one, so a retry is safe. When resumed=true, tell the user which company you are continuing (the response carries its name) instead of assuming it is the one they just described. If they say they want a DIFFERENT, additional company, call again with force_new=true — that is the only time to set it; never set it to retry. Before walking the steps, briefly understand the user's business, experience, and funding (one question at a time), then give a tailored recommendation. Keep the formation_id and pass it to every later step. Call this exactly ONCE per formation — never start a second one to resume. When a later step needs sign-in, let the user connect and retry with the SAME formation_id; signing in automatically claims the in-progress formation, so it is never lost.

Input Schema

Name	Required	Description
`source`	No
`forceNew`	No
`sessionId`	No	UUID value wrapper.
`attribution`	No
`inviteToken`	No
`referralCode`	No

Output Schema

Name	Required	Description	Default
`status`	No
`resumed`	No
`sessionId`	No
`companyName`	No
`currentStep`	No
`formationId`	No
`partnerPays`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedInput schema / properties / attribution

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed12 schema fields changedSep 10, 2026

addedInput schema / properties / inviteToken

Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}

changedOutput schema / properties / currentStep / enum

Previous value: -[
-  "FORMATION_STEP_UNSPECIFIED",
-  "FORMATION_STEP_CREATED",
-  "FORMATION_STEP_BUSINESS_DESCRIBED",
-  "FORMATION_STEP_STATE_SELECTED",
-  "FORMATION_STEP_TYPE_SELECTED",
-  "FORMATION_STEP_ENDING_SELECTED",
-  "FORMATION_STEP_NAME_SET",
-  "FORMATION_STEP_NAME_CHECKED",
-  "FORMATION_STEP_COMPANY_ADDRESS_SET",
-  "FORMATION_STEP_AGENT_SET",
-  "FORMATION_STEP_SHARES_SET",
-  "FORMATION_STEP_SHAREHOLDERS_ADDED",
-  "FORMATION_STEP_AUTHORIZED_PARTY_SET",
-  "FORMATION_STEP_CERTIFICATE_GENERATED",
-  "FORMATION_STEP_CERTIFICATE_APPROVED",
-  "FORMATION_STEP_COMPLETED"
-]New value: +[
+  "FORMATION_STEP_UNSPECIFIED",
+  "FORMATION_STEP_CREATED",
+  "FORMATION_STEP_BUSINESS_DESCRIBED",
+  "FORMATION_STEP_STATE_SELECTED",
+  "FORMATION_STEP_TYPE_SELECTED",
+  "FORMATION_STEP_ENDING_SELECTED",
+  "FORMATION_STEP_NAME_SET",
+  "FORMATION_STEP_NAME_CHECKED",
+  "FORMATION_STEP_COMPANY_ADDRESS_SET",
+  "FORMATION_STEP_AGENT_SET",
+  "FORMATION_STEP_SHARES_SET",
+  "FORMATION_STEP_SHAREHOLDERS_ADDED",
+  "FORMATION_STEP_AUTHORIZED_PARTY_SET",
+  "FORMATION_STEP_CERTIFICATE_GENERATED",
+  "FORMATION_STEP_CERTIFICATE_APPROVED",
+  "FORMATION_STEP_COMPLETED",
+  "FORMATION_STEP_FOUNDER_PROFILE_SET",
+  "FORMATION_STEP_TEAM_EQUITY_SET",
+  "FORMATION_STEP_DEAL_CONFIRMED",
+  "FORMATION_STEP_BANKING_INTENT_SET",
+  "FORMATION_STEP_SIGNED",
+  "FORMATION_STEP_INDUSTRY_SET"
+]

addedOutput schema / properties / formationId / anyOf

Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / formationId / description
```
Removed value: -"UUID value wrapper."
```

removedOutput schema / properties / formationId / properties

Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}

removedOutput schema / properties / formationId / type
```
Removed value: -"object"
```
addedOutput schema / properties / partnerPays
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / sessionId / anyOf

Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / sessionId / description
```
Removed value: -"UUID value wrapper."
```

removedOutput schema / properties / sessionId / properties

Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}

removedOutput schema / properties / sessionId / type
```
Removed value: -"object"
```

changedOutput schema / properties / status / enum

Previous value: -[
-  "FORMATION_STATUS_UNSPECIFIED",
-  "FORMATION_STATUS_INITIATED",
-  "FORMATION_STATUS_IN_PROGRESS",
-  "FORMATION_STATUS_PAYMENT_PENDING",
-  "FORMATION_STATUS_PAYMENT_COMPLETE",
-  "FORMATION_STATUS_FILING_IN_PROGRESS",
-  "FORMATION_STATUS_COMPLETED",
-  "FORMATION_STATUS_FAILED",
-  "FORMATION_STATUS_CANCELLED"
-]New value: +[
+  "FORMATION_STATUS_UNSPECIFIED",
+  "FORMATION_STATUS_INITIATED",
+  "FORMATION_STATUS_IN_PROGRESS",
+  "FORMATION_STATUS_PAYMENT_PENDING",
+  "FORMATION_STATUS_PAYMENT_COMPLETE",
+  "FORMATION_STATUS_FILING_IN_PROGRESS",
+  "FORMATION_STATUS_COMPLETED",
+  "FORMATION_STATUS_FAILED",
+  "FORMATION_STATUS_CANCELLED",
+  "FORMATION_STATUS_IMPORTED"
+]

Changed1 schema field changedAug 17, 2026

addedInput schema / properties / sessionId

Added value: +{
+  "description": "UUID value wrapper.",
+  "properties": {
+    "value": {
+      "format": "uuid",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 13, 2026

changedInput schema / properties / source / enum

Previous value: -[
-  "FORMATION_SOURCE_UNSPECIFIED",
-  "FORMATION_SOURCE_WEB",
-  "FORMATION_SOURCE_MCP",
-  "FORMATION_SOURCE_CLI",
-  "FORMATION_SOURCE_AGENTS",
-  "FORMATION_SOURCE_CONVERSATIONAL",
-  "FORMATION_SOURCE_NAME_GEN",
-  "FORMATION_SOURCE_WHATSAPP",
-  "FORMATION_SOURCE_TELEGRAM"
-]New value: +[
+  "FORMATION_SOURCE_UNSPECIFIED",
+  "FORMATION_SOURCE_WEB",
+  "FORMATION_SOURCE_MCP",
+  "FORMATION_SOURCE_CLI",
+  "FORMATION_SOURCE_AGENTS",
+  "FORMATION_SOURCE_CONVERSATIONAL",
+  "FORMATION_SOURCE_NAME_GEN",
+  "FORMATION_SOURCE_WHATSAPP",
+  "FORMATION_SOURCE_TELEGRAM",
+  "FORMATION_SOURCE_LANDING"
+]

First observedAug 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare openWorldHint=false and destructiveHint=false. The description adds substantial behavior the annotations cannot: it runs anonymously with no auth, is idempotent (re-calls resume rather than duplicate, resumed=true), retry-safe, returns a formation_id + ordered steps, and explains that signing in later claims the in-progress formation.

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 critical routing and idempotency guidance, and nearly every sentence earns its place. However, the resume/'call exactly ONCE' behavior is restated several times, adding mild redundancy in an already long description.

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 formation-entry tool with an output schema present, the description covers what matters: auth posture, idempotency, error recovery, and downstream formation_id threading. Return values need not be detailed since an output schema exists, yet it still notes formation_id and steps.

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 only 17% and there are 6 parameters, so the description carries the burden. It explains forceNew thoroughly (the key behavioral param) and hints at the anonymous context, but source, sessionId, attribution, inviteToken, and referralCode are left entirely undocumented in both schema and 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+resource (start/begin a company formation) and explicitly positions itself as 'THE entry point for a new company formation.' It distinguishes itself from siblings by name (company_get_my_companies, formation_get_list_formations) and explains why they are different.

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-call ('whenever the user wants to start, create, or form a company'), when-not-to-call ('Do NOT call company_get_my_companies or formation_get_list_formations first'), plus precise rules for the retry/resume path and the sole condition for force_new=true. Nothing 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.

All Lovie Company Formation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.