FilingDesk Data

Submit the formation order

submit_order

Submit a real formation order to FilingDesk. THIS HAS A REAL-WORLD EFFECT: it creates an order and notifies a FilingDesk specialist. Only call after preview_order and after the user has explicitly confirmed the summary. Nothing is charged now — a specialist reviews the order, verifies the name, and emails a payment link. Returns the order reference.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	The customer's email.
`phone`	No	Optional phone number.
`state`	Yes	Two-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC.
`fullName`	Yes	The customer's full name.
`entityType`	Yes	Entity type, e.g. "LLC", or "Not sure".
`description`	No	What the business does. Optional.
`businessName`	Yes	Proposed company name.
`userConfirmed`	Yes	Must be true. Set only after the user has seen the preview_order summary and explicitly agreed to submit.

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond annotations by explaining the real-world effect: creates an order, notifies a specialist, nothing charged now, and a payment link is emailed later. It also mentions the return of the order reference. These behavioral details are not present in the annotations, which only state readOnlyHint=false and openWorldHint=true.

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?

The description is compact and front-loaded with purpose. It contains five sentences, each adding value, though the capitalized 'THIS HAS A REAL-WORLD EFFECT' is slightly embellished. Overall, it is well-structured for the complexity.

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 description is complete for a side-effectful tool: it covers when to call, the real-world impact, the subsequent review process, and the return value (order reference). Even without an output schema, the agent has enough context to invoke the tool correctly.

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 coverage is 100% and parameter descriptions are detailed. The description adds no additional parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states the tool submits a real formation order to FilingDesk, with a specific verb and resource. It distinguishes itself from sibling tools like preview_order by noting it should be called after preview_order and by emphasizing the real-world effect.

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?

Explicit usage guidance is provided: 'Only call after preview_order and after the user has explicitly confirmed the summary.' This clearly dictates when to use the tool versus alternatives, and the sequencing with preview_order is highlighted.

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

All FilingDesk Data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but get_llc_fees and compare_llc_costs both return cost data, which could cause mis-selection for single-state fee queries. Similarly, check_llc_name and list_filing_states both touch on name-checking capabilities, though one actually performs a check and the other lists support.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (check_, compare_, get_, list_, preview_, submit_). The verbs are varied but the structure is uniform and readable.

Tool Count5/5

8 tools is well-scoped for the LLC research-to-order workflow. Each tool earns its place, covering name checks, cost comparisons, fee details, deadlines, filing capabilities, and the order preview/submit flow.

Completeness4/5

The toolset covers the entire pre-sales and order placement journey: research (name, fees, costs, deadlines, options, filing states) and submission (preview, submit). Minor gap: there is no post-submission order status tool, but this may be outside the server's purpose.

Resources

Need Help?