Corpus Law

Validate and hand off a formation draft

formation.handoff

Read-onlyIdempotent

Validate a formation draft and generate the prefilled handoff link on corpuslaw.us. Pass EVERYTHING you have collected (people, address, management, EIN answers, state-specific answers — see formation.requirements for the checklist). The response says exactly what is still missing — keep collecting and call again until COMPLETE, then give the user the link: it opens the formation agent with every detail pre-loaded, so they only review, sign in, and pay. Free; does not consume credits.

Input Schema

TableJSON Schema

Name	Required	Description
`ein`	No	Optional EIN (federal tax ID) add-on, when available — formation.requirements says whether it can currently be sold and at what price. Never quote a remembered EIN price; use the one that call returns. Set wanted=true/false once the user decides. NEVER include a Social Security Number anywhere — the founder types it into a secure panel on corpuslaw.us, never in chat.
`state`	Yes	Two-letter US state code, e.g. 'MS', 'WY', 'DE'.
`parties`	No	The people. LLC: at least one 'member' and an 'organizer' (same person may hold both roles — pass two entries). Nonprofit: an 'incorporator' and at least 3 'director' entries (plus officers where the state requires them).
`naicsCode`	No	NAICS industry code, 2–6 digits (use formation.lookup_naics to find it).
`nonprofit`	No	Nonprofit-only fields.
`entityType`	Yes	Entity type to form.
`management`	No	LLC management type.
`contactEmail`	No	Founder contact email.
`proposedName`	No	Proposed company name.
`referral_code`	No	Your referral code from account.status, if you have one. The founder saves 25% of the Corpus service fee and the order is credited to your code. Omit it if you do not have one — an absent or unrecognised code changes nothing about the link.
`principalOffice`	No	Principal office address (street, city, state required for a complete draft).
`businessActivity`	No	In one plain sentence, what the business actually does, in the founder's words (not the company name). Corpus researches the licenses and permits that apply from this.
`stateSpecificAnswers`	No	Per-state quirk answers under the EXACT keys shown by formation.requirements (e.g. "would_you_like_to_list_members_managers_on_the_state_record"). Values are strings or booleans.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Human-readable tool result (also mirrored in content[].text).
`isError`	No	True when the tool could not complete successfully.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 12, 2026

addedInput schema / properties / businessActivity

Added value: +{
+  "description": "In one plain sentence, what the business actually does, in the founder's words (not the company name). Corpus researches the licenses and permits that apply from this.",
+  "maxLength": 500,
+  "type": "string"
+}

Changed1 schema field changedSep 4, 2026

changedInput schema / properties / ein / description

Previous value: -"Optional $75 EIN (federal tax ID) add-on, when available — formation.requirements says whether it can currently be sold. Set wanted=true/false once the user decides. NEVER include a Social Security Number anywhere — the founder types it into a secure panel on corpuslaw.us, never in chat."New value: +"Optional EIN (federal tax ID) add-on, when available — formation.requirements says whether it can currently be sold and at what price. Never quote a remembered EIN price; use the one that call returns. Set wanted=true/false once the user decides. NEVER include a Social Security Number anywhere — the founder types it into a secure panel on corpuslaw.us, never in chat."

First observedAug 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description confirms consistency by framing this as a validate-and-generate-link step. It adds genuinely new behavioral context: the call is free and consumes no credits, the response reports exactly what is missing, and the returned link opens the formation agent with details pre-loaded for review/sign-in/payment.

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?

Purpose is front-loaded in the first clause, followed by collection instructions, the iterative loop, and the cost note; every sentence carries operational value. It is dense with parentheticals and reads as a run-on, but nothing is wasted.

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 13-parameter, nested, open-world tool with an output schema, the description supplies the workflow (iterate until COMPLETE), the cost model, the checklist dependency (formation.requirements), and the downstream UX of the link. The sensitive-data constraint (never pass an SSN) is handled in the schema, so nothing essential 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?

Schema description coverage is already 100%, so the baseline is 3. The description adds useful framing beyond the schema by enumerating the categories to pass (people, address, management, EIN answers, state-specific answers) and by tying state-specific keys to formation.requirements rather than leaving the agent to guess key names.

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?

States a specific two-part verb+resource: validate a formation draft and generate the prefilled handoff link. It situates itself against siblings by pointing to formation.requirements for the checklist, so an agent can tell what this tool does that the others do not.

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?

Gives a clear usage loop — pass everything collected, read the missing-items response, keep calling until COMPLETE, then hand the link to the user — and routes the agent to formation.requirements for the checklist. There is no explicit 'when not to use' or preconditions (e.g. minimum draft state), so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Corpus Law 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.

Resources

Need Help?