formation_set_registered_agentSets the registered agent for the formation. Pass use_default = true to use Lovie's included registered agent (recommended for most founders), or use_default = false with an agent to supply a custom one.
| Name | Required | Description | Default |
|---|---|---|---|
| agent | No | ||
| useDefault | No | ||
| formationId | Yes | UUID value wrapper. |
| Name | Required | Description | Default |
|---|---|---|---|
| formationId | No | ||
| registeredAgent | No |
Changes observed during successful MCP inspections.
Input schema / properties / agent / properties / address / properties / city / patternRemoved value: -"^[A-Za-z .'-]+$"Input schema / properties / agent / properties / address / properties / country / maxLengthRemoved value: -2Input schema / properties / agent / properties / address / properties / country / patternPrevious value: -"^[A-Z]*$"New value: +"^[A-Z]{2}$"Input schema / properties / agent / properties / address / properties / county / patternRemoved value: -"^[A-Za-z ]*$"Input schema / properties / agent / properties / address / properties / state / maxLengthPrevious value: -50New value: +100Input schema / properties / agent / properties / address / properties / state / minLengthRemoved value: -1Input schema / properties / agent / properties / address / properties / state / patternRemoved value: -"^[A-Za-z ]+$"Input schema / properties / agent / properties / address / properties / street1 / patternRemoved value: -"^[A-Za-z0-9 .,#/-]+$"Input schema / properties / agent / properties / address / properties / street2 / patternRemoved value: -"^[A-Za-z0-9 .,#/-]*$"Input schema / properties / agent / properties / address / properties / zipCode / maxLengthPrevious value: -10New value: +20Input schema / properties / agent / properties / address / properties / zipCode / minLengthRemoved value: -5Input schema / properties / agent / properties / address / properties / zipCode / patternRemoved value: -"^[0-9]{5}(-[0-9]{4})?$"Input schema / properties / agent / properties / email / patternPrevious 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,})?$"Output schema / properties / formationId / anyOfAdded value: +[
+ {
+ "description": "UUID value wrapper.",
+ "properties": {
+ "value": {
+ "format": "uuid",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / formationId / descriptionRemoved value: -"UUID value wrapper."Output schema / properties / formationId / propertiesRemoved value: -{
- "value": {
- "format": "uuid",
- "type": "string"
- }
-}Output schema / properties / formationId / typeRemoved value: -"object"Output schema / properties / registeredAgent / anyOfAdded 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"
+ }
+]Output schema / properties / registeredAgent / propertiesRemoved 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"
- }
-}Output schema / properties / registeredAgent / requiredRemoved value: -[
- "name"
-]Output schema / properties / registeredAgent / typeRemoved value: -"object"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only indicate non-destructive and closed-world behavior, so the description must carry the behavioral burden. It explains the default vs. custom agent branch but does not disclose side effects like overwriting an existing agent, prerequisites, or what happens if useDefault is omitted. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. It front-loads the verb and resource, then efficiently explains both invocation modes with a recommendation, making it easy to parse and act on.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema and annotations reduce the burden, but the description leaves gaps: it doesn't specify behavior when useDefault is omitted, relies on 'or' to imply mutual exclusivity, and contains a parameter-naming mismatch. An agent could call this correctly but only by reconciling the description with the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is low (33%), so the description partially compensates by explaining the useDefault/agent relationship. However, it uses 'use_default' (snake_case) while the schema defines 'useDefault' (camelCase), creating a potentially confusing mismatch, and it does not add meaning for formationId.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb+resource: 'Sets the registered agent for the formation.' It clearly states the action, the target, and the two modes of operation, which distinguishes it from other formation tools like formation_purchase_registered_agent and formation_set_company_setup_details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear operational guidance: use use_default=true with Lovie's included agent (recommended for most founders) or use_default=false with a custom agent. It does not explicitly contrast with sibling tools, but it gives a usable decision rule within the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.