Lovie Company Formation

Set Share Structure

formation_set_share_structure

Sets the C-Corp share structure and returns the resulting total authorized capital. Pass use_default = true for the standard startup setup (10,000,000 shares at $0.0001 par), or use_default = false with authorized_shares and par_value for a custom structure. C-Corp only.

Input Schema

TableJSON Schema

Name	Required	Description
`parValue`	No
`useDefault`	No
`formationId`	Yes	UUID value wrapper.
`authorizedShares`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`formationId`	No
`totalCapital`	No
`shareStructure`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 10, 2026

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 / shareStructure / anyOf

Added value: +[
+  {
+    "properties": {
+      "authorizedShares": {
+        "type": "string"
+      },
+      "isDefault": {
+        "type": "boolean"
+      },
+      "parValuePerShare": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / shareStructure / properties

Removed value: -{
-  "authorizedShares": {
-    "type": "string"
-  },
-  "isDefault": {
-    "type": "boolean"
-  },
-  "parValuePerShare": {
-    "type": "string"
-  }
-}

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

First observedAug 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description communicates that the tool mutates the share structure and returns the resulting authorized capital, which is useful beyond the sparse annotations. It does not mention whether the call overwrites existing settings, has approval requirements, or affects other formation-related data, so the behavioral picture is incomplete.

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?

The description is brief and front-loaded: it states the action and return value first, then gives the default/custom branching, then the C-Corp constraint. There is no filler or repeated schema information.

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 four-parameter mutation tool with an output schema, the description covers the core decision (default vs. custom), the return behavior, and an important pre-condition. It does not explain the exact required combination of custom values or potential failure modes, but those are reasonably inferable from the schema and the explanation given.

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?

The description adds genuinely useful semantics by defining the default structure as 10,000,000 shares at $0.0001 par and explaining the custom structure path. However, it references use_default, authorized_shares, and par_value while the schema exposes useDefault, authorizedShares, and parValue; this naming mismatch is a correctness risk and prevents full compensation for the low schema coverage.

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?

The description clearly says the tool sets the C-Corp share structure and returns total authorized capital, which is a specific verb and resource. It does not explicitly distinguish itself from closely related sibling tools like cap_table_set_cap_table_authorized_shares, so it falls short of a 5.

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?

It gives explicit parameter-level usage guidance: useDefault=true for the standard startup setup and useDefault=false with custom authorized shares and par value. It also states C-Corp only. However, it does not name when to prefer a different tool over this one.

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.