Lovie Company Formation

Generate Certificate

formation_generate_certificate

Prepares the Certificate of Formation/Incorporation as a review checkpoint before filing. This is a confirmation step, NOT a downloadable document — the official, state-issued certificate is produced only after payment and state filing, so do NOT present a download link here. Summarize the formation details for the user to review, then call formation_approve_certificate only once they explicitly confirm the details are correct.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`expiresAt`	No
`downloadUrl`	No
`formationId`	No
`certificateId`	No
`minutesRemaining`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 10, 2026

addedOutput schema / properties / expiresAt / anyOf

Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / expiresAt / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / expiresAt / type
```
Removed value: -"string"
```

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?

Annotations indicate openWorldHint=false and destructiveHint=false, but do not state read-only. The description adds transparency by explaining that this is a confirmation step, that it does not produce an official certificate, and that it should not present a download link. It also specifies the workflow (summarize details, wait for explicit confirmation, then call approve). This goes beyond the annotations, though it does not explicitly state whether the tool has side effects (e.g., marking a status).

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?

The description is well-structured and front-loaded with the core purpose, then clarifies exclusions and the next action. Every sentence earns its place—no fluff, and the critical distinction (not a download) is highlighted early. It is appropriately sized for the information it conveys.

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 simple tool with one parameter and an output schema, the description fully covers what an agent needs to call it correctly: what it does, what it does not do, how to present it, and the follow-up action. The existence of an output schema means the return format doesn't need to be described. Nothing essential is missing.

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?

The schema already documents the single parameter formationId as a UUID value wrapper, so coverage is 100%. The description does not add any additional meaning about the parameter, which is acceptable given its obvious purpose. Baseline of 3 is appropriate because the schema carries the burden.

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: 'Prepares the Certificate of Formation/Incorporation as a review checkpoint before filing.' It clearly differentiates from siblings by explicitly noting it is NOT a downloadable document and that the official certificate comes later. This leaves no ambiguity about the tool's role.

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

Usage Guidelines5/5

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

The description explicitly says when to use it (as a review checkpoint before filing) and when not to (not for downloads). It also names the exact alternative tool (formation_approve_certificate) and the condition for calling it, providing clear routing to the correct next step.

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.