Lovie Company Formation

Get Formation Quote

formation_get_formation_quote

Read-only

Returns what forming a company costs, priced live, with includes listing what the price covers. Creates nothing and charges nothing. Use this whenever the user asks about price instead of quoting a figure from memory — it is ONE flat all-inclusive one-time payment, the same in every state, so there is no plan, no cadence, no add-on and no second charge to describe. The state argument is accepted for compatibility and does not change the price.

Input Schema

Name	Required	Description	Default
`state`	No

Output Schema

Name	Required	Description	Default
`includes`	No
`lineItems`	No
`totalCents`	No
`totalDisplay`	No
`subtotalCents`	No
`subtotalDisplay`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026
- removedOutput schema / properties / filingFeeCents
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / filingFeeDisplay
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / includes
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
First observedAug 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

It goes far beyond the annotations by explicitly stating 'Creates nothing and charges nothing' and defining the financial model: 'ONE flat all-inclusive one-time payment.' It also clarifies that the state argument does not affect the price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

While slightly verbose, every sentence is necessary to eliminate ambiguity regarding the pricing model (e.g., clarifying there is 'no plan, no cadence, no add-on'), making the detail worthwhile.

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?

The definition is complete for a quoting function, fully detailing the constraints of the quote (flat-rate, non-charging, coverage list) and the behavior of the only input parameter.

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

Parameters5/5

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

Since schema description coverage is 0%, the description is crucial. It explicitly explains the role of the 'state' argument, stating it is accepted only for compatibility and does not change the price.

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 uses a specific verb ('Returns') and clearly defines the resource (formation cost), detailing that it provides a 'live' price and includes a list of coverage items.

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?

It provides clear guidance on when to invoke the tool: specifically when the user asks about price, contrasting this need with simply 'quoting a figure from memory'.

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.