Lovie Company Formation

Purchase Formation

formation_purchase_formation

Destructive

PurchaseFormation places the CorpTools formation filing order: it claims the order atomically, adds the filing to the cart, and checks out with the stored payment method. Reviewer-only. Checkout moves money and is never retried once it succeeds.

Input Schema

TableJSON Schema

Name	Required	Description
`formData`	No
`formationId`	Yes	UUID value wrapper.
`filingMethodId`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`invoiceIds`	No
`cartItemIds`	No
`formationId`	No
`corpToolsCompanyId`	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.3/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description explicitly discloses that checkout 'moves money' and is 'never retried once it succeeds,' which conveys irreversibility and financial impact. The atomic claim behavior is also disclosed. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with no filler: the first fronts the action and flow, the second states the permission constraint, the third warns about financial irreversibility. Every clause earns its place.

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?

Given the output schema and destructive annotation, the description covers the important operational and risk context well. It falls short only in parameter-level guidance, but overall an agent can understand what invoking this tool entails.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, and the description does not explain formData, filingMethodId, or how formationId relates to the order flow. The property names give minimal hints, but the description fails to compensate for the poorly documented schema.

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 verb and resource: it 'places the CorpTools formation filing order' and details the atomic claim, cart addition, and checkout flow. This clearly distinguishes it from siblings like formation_get_formation_purchase_quote and formation_confirm_payment.

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?

The description gives clear operational context including the reviewer-only restriction and the fact that checkout uses the stored payment method. It does not explicitly name alternatives or when-not-to-use conditions, but the context is enough to infer appropriate use.

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.