Lovie Company Formation

Set Registered Agent

formation_set_registered_agent

Sets the registered agent for the formation. Pass use_default = true to use Lovie's registered agent, which the formation price includes at no extra charge (recommended for most founders), or use_default = false with an agent to supply a custom one. Either way the price is the same.

Input Schema

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

Output Schema

Name	Required	Description	Default
`formationId`	No
`registeredAgent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedSep 10, 2026

removedInput schema / properties / agent / properties / address / properties / city / pattern
```
Removed value: -"^[A-Za-z .'-]+$"
```
removedInput schema / properties / agent / properties / address / properties / country / maxLength
```
Removed value: -2
```
changedInput schema / properties / agent / properties / address / properties / country / pattern
```
Previous value: -"^[A-Z]*$"New value: +"^[A-Z]{2}$"
```
removedInput schema / properties / agent / properties / address / properties / county / pattern
```
Removed value: -"^[A-Za-z ]*$"
```
changedInput schema / properties / agent / properties / address / properties / state / maxLength
```
Previous value: -50New value: +100
```
removedInput schema / properties / agent / properties / address / properties / state / minLength
```
Removed value: -1
```
removedInput schema / properties / agent / properties / address / properties / state / pattern
```
Removed value: -"^[A-Za-z ]+$"
```
removedInput schema / properties / agent / properties / address / properties / street1 / pattern
```
Removed value: -"^[A-Za-z0-9 .,#/-]+$"
```
removedInput schema / properties / agent / properties / address / properties / street2 / pattern
```
Removed value: -"^[A-Za-z0-9 .,#/-]*$"
```
changedInput schema / properties / agent / properties / address / properties / zipCode / maxLength
```
Previous value: -10New value: +20
```
removedInput schema / properties / agent / properties / address / properties / zipCode / minLength
```
Removed value: -5
```
removedInput schema / properties / agent / properties / address / properties / zipCode / pattern
```
Removed value: -"^[0-9]{5}(-[0-9]{4})?$"
```

changedInput schema / properties / agent / properties / email / pattern

Previous value: -"^[a-zA-Z0-9._%+-]*@?[a-zA-Z0-9.-]*\\.?[a-zA-Z]*$"New value: +"^([a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,})?$"

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

Added value: +[
+  {
+    "properties": {
+      "address": {
+        "anyOf": [
+          {
+            "properties": {
+              "city": {
+                "type": "string"
+              },
+              "country": {
+                "type": "string"
+              },
+              "county": {
+                "type": "string"
+              },
+              "state": {
+                "type": "string"
+              },
+              "street1": {
+                "type": "string"
+              },
+              "street2": {
+                "type": "string"
+              },
+              "zipCode": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "email": {
+        "type": "string"
+      },
+      "isDefault": {
+        "type": "boolean"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "description": "Human-readable name (1-255 Unicode chars).",
+            "properties": {
+              "value": {
+                "maxLength": 255,
+                "minLength": 1,
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "phone": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / registeredAgent / properties

Removed value: -{
-  "address": {
-    "properties": {
-      "city": {
-        "type": "string"
-      },
-      "country": {
-        "type": "string"
-      },
-      "county": {
-        "type": "string"
-      },
-      "state": {
-        "type": "string"
-      },
-      "street1": {
-        "type": "string"
-      },
-      "street2": {
-        "type": "string"
-      },
-      "zipCode": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "email": {
-    "type": "string"
-  },
-  "isDefault": {
-    "type": "boolean"
-  },
-  "name": {
-    "description": "Human-readable name (1-255 Unicode chars).",
-    "properties": {
-      "value": {
-        "maxLength": 255,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "phone": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / registeredAgent / required
```
Removed value: -[
-  "name"
-]
```
removedOutput schema / properties / registeredAgent / 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?

Annotations declare destructiveHint=false and openWorldHint=false but no readOnlyHint, so the mutation-safety profile is only partially covered. The description adds useful behavioral context (the registered agent is included in the formation price at no extra charge, and price is identical either way), but omits whether the setting can be overwritten, idempotency, or any permission requirements.

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 sentences with the core action front-loaded, then the default/custom branches, then the price reassurance. The trailing "Either way the price is the same" is mildly redundant with "at no extra charge" but reinforces a decision-relevant fact.

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?

An output schema exists, so return-value explanation is not required, and the description covers the key decision an agent must make for a mutation tool. Given the nested `agent` object and low schema coverage, it could say more about the custom-agent fields, but the essentials are present.

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?

With only 33% schema coverage, the description compensates well by explaining the required `useDefault`/`agent` relationship and the recommended default path. The `agent` nested fields are left to the schema and the parameter is named "use_default" versus the schema's `useDefault`, a minor casing mismatch, but the core semantics are conveyed.

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 states a specific verb and resource ("Sets the registered agent for the formation"), making the operation immediately identifiable. It doesn't explicitly distinguish itself from the sibling formation_purchase_registered_agent or list_agents, so sibling differentiation relies on the reader's inference.

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 clear decision guidance for the main choice: use_default=true for Lovie's agent ("recommended for most founders") and use_default=false with a custom `agent`. However, it does not address when to use this tool versus related siblings such as formation_purchase_registered_agent, nor any when-not conditions.

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.