Lovie Company Formation

Set Entity Ending

formation_set_entity_ending

Sets the company's legal entity ending — the suffix that appears in the full legal name (e.g. "Inc.", "Corporation", "Co." for a C-Corp; "LLC", "L.L.C." for an LLC). Use one of the valid endings returned by formation_set_company_type. Set this BEFORE the company name so the full legal name is derived correctly.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`formationId`	No
`entityEnding`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

First observedAug 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the sparse annotations, the description reveals that the ending is constrained by the company type and that the call affects how the full legal name is derived. It does not describe overwrite behavior or validation failures, but for a non-destructive setter this is adequate.

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 deliver the definition, examples, value constraint, prerequisite, and ordering rule with no filler. The key instruction is front-loaded.

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 two-parameter setter with an output schema, the description covers the meaningful parameter, the prerequisite sibling call, and the necessary ordering. Nothing critical for invoking the tool correctly is missing.

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?

The ending parameter is richly described with semantic meaning, examples, and a constrained source of valid values, compensating for the schema's bare string type. The formationId parameter is left to the schema's minimal 'UUID value wrapper' description, but it is an obvious identifier parameter.

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?

The description states a specific operation ('Sets the company's legal entity ending') and provides concrete examples ('Inc.', 'Corporation', 'Co.', 'LLC') that make the resource unmistakable. It also distinguishes this tool from related setters like formation_set_company_name and formation_set_company_type by focusing on the suffix that appears in the full legal name.

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 operational guidance: use only valid endings returned by formation_set_company_type and call this before setting the company name. It does not explicitly list when-not-to-use cases or name an alternative tool for setting the name, but the prerequisite and ordering are clear.

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.