Lovie Company Formation

Get Formation Purchase Quote

formation_get_formation_purchase_quote

Read-only

GetFormationPurchaseQuote returns the CorpTools filing product, methods, parsed form schema, prefilled values, and missing required fields for a formation (non-DE/WY states). Reviewer-only; no side effects beyond ensuring a CorpTools company record exists.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`prefilled`	No
`productId`	No
`productName`	No
`schemaFields`	No
`filingMethods`	No
`missingFields`	No
`corpToolsCompanyId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026
- removedOutput schema / properties / prefilled / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / prefilled / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / prefilled / type
```
Removed value: -"object"
```
First observedAug 11, 2026

TDQS

B3.2/5.0

Behavior1/5

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

The description says 'no side effects beyond ensuring a CorpTools company record exists,' which implies a possible write/create behavior. This directly contradicts the annotation readOnlyHint=true. Because the description admits a side effect that the annotation claims does not happen, this is an annotation contradiction and a serious source of agent confusion.

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-loaded with the return value and then adding role and side-effect context. Every sentence earns its place with no filler or redundancy.

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?

With an output schema present, the description need not explain return values in detail. It covers scope, role, and side effects. The main gap is the absence of sibling-tool differentiation and the tension with the readOnlyHint annotation, but the description itself is otherwise complete for a single-parameter read-oriented tool.

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?

Schema description coverage is 100%: formationId is documented as a 'UUID value wrapper.' The description does not add parameter-level detail, but the schema already fully covers it, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: it 'returns the CorpTools filing product, methods, parsed form schema, prefilled values, and missing required fields' for a formation. It also scopes to non-DE/WY states. It does not explicitly distinguish itself from siblings like formation_get_formation_quote, but the object it returns is specific enough.

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?

It gives some usage context: 'Reviewer-only' and restricting to non-DE/WY states. However, it does not explain when to choose this tool versus nearby siblings such as formation_get_formation_quote or formation_get_filing_fee, leaving the alternative-selection guidance implied at best.

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.