Lovie Company Formation

Set State

formation_set_state

Sets the formation's state of formation. Every US state and DC is supported — pass the two-letter code (e.g. "TX", "DE", "WY"). Returns the entity types available for that state.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No
`formationId`	Yes	UUID value wrapper.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No
`formationId`	No
`stateDescription`	No
`availableCompanyTypes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 10, 2026

addedOutput schema / properties / availableCompanyTypes / items / properties / description / anyOf

Added value: +[
+  {
+    "description": "Free-form description (max 5000 chars).",
+    "properties": {
+      "value": {
+        "maxLength": 5000,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / availableCompanyTypes / items / properties / description / description
```
Removed value: -"Free-form description (max 5000 chars)."
```
removedOutput schema / properties / availableCompanyTypes / items / properties / description / properties
```
Removed value: -{
-  "value": {
-    "maxLength": 5000,
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / availableCompanyTypes / items / properties / description / type
```
Removed value: -"object"
```

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"
```

First observedAug 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already cover non-destructiveness and closed world, and the description adds that all states/DC are supported and that entity types are returned. It does not disclose overwrite behavior, idempotency, or what happens when state is omitted.

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?

Two sentences front-load the action and necessary code format, then state the return value. No filler or repetition beyond a minor formation/formation phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A competent agent can invoke this tool with formationId and a state code, and the output schema covers the return. Yet the optionality of state and the meaning of formationId are under-specified for a mutation-like tool with sibling formation_set_* tools.

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?

It gives valuable format guidance for the state parameter (two-letter code with examples) and explains the return value. However, formationId's role is left to inference, and the description's 'pass the two-letter code' sits awkwardly against the schema making state optional.

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?

Description names the action (sets), resource (formation's state of formation), and scope (all US states + DC) with examples. It clearly distinguishes this from sibling formation_set_* tools such as formation_set_company_name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied by the verb+resource: when an agent needs to set a formation's jurisdiction. However, it does not explicitly state when to use it versus alternatives or when not to use it.

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.