Skip to main content
Glama
Sign In

FilingDesk Data

by com.filingdesk
OverviewDiscussionsAdmin

Submit the formation order

submit_order
Destructive

Submits a formation order to FilingDesk. THIS HAS A REAL-WORLD EFFECT: it records the order, notifies a FilingDesk specialist, and may send an automatic order-confirmation email to the customer's email address. The specialist then reviews the order, confirms name availability and the price, and emails a payment link. Nothing is charged at submission. Call only after preview_order, once the user has explicitly confirmed that summary (userConfirmed: true). Returns the order reference (FD-…).

Input Schema

NameRequiredDescriptionDefault
emailYesThe customer's email.
phoneYesThe customer's phone number (required).
stateYesTwo-letter state code or full state name, e.g. "WY" or "Wyoming". All 50 states + DC.
fullNameYesThe customer's full name.
entityTypeYesEntity type, e.g. "LLC", or "Not sure".
descriptionNoWhat the business does. Optional.
businessNameYesProposed company name.
userConfirmedYesMust be true. Set only after the user has seen the preview_order summary and explicitly agreed to submit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / phone / description
      Previous value: -"Optional phone number."New value: +"The customer's phone number (required)."
    • changedInput schema / required
      Previous value: -[
-  "businessName",
-  "state",
-  "entityType",
-  "fullName",
-  "email",
-  "userConfirmed"
-]New value: +[
+  "businessName",
+  "state",
+  "entityType",
+  "fullName",
+  "email",
+  "phone",
+  "userConfirmed"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the concrete real-world effects: recording the order, notifying a specialist, possibly emailing the customer, and that nothing is charged at submission. This is exactly the kind of side-effect context the destructiveHint/openWorldHint flags cannot convey. It stops short of describing failure modes or how to retry after a failed submission, so it is not quite a 5.

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?

Front-loads the action and the critical real-world warning, and every sentence carries information (side effects, no-charge note, gating condition, return value). Slightly dense, but no sentence is filler.

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 mutating tool with full annotation coverage and a complete schema, the description supplies the missing pieces: the workflow prerequisite, the confirmation requirement, the real-world consequence, and the return format (order reference FD-…). Nothing needed to invoke it safely is absent.

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%, so the schema already documents all eight fields, including the exact semantics of userConfirmed. The description only reinforces the userConfirmed gate and notes the returned order reference, adding little parameter meaning beyond the schema; baseline 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?

States a specific verb and resource ('Submits a formation order to FilingDesk') and immediately distinguishes itself from the sibling preview_order by describing the actual submission side-effect. An agent can tell this apart from preview_order and the informational siblings without opening any schema.

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?

Explicitly gates usage: 'Call only after preview_order, once the user has explicitly confirmed that summary (userConfirmed: true).' It names the prerequisite tool and the exact condition that selects this tool, leaving nothing to inference.

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

All FilingDesk Data toolsInspect
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