Skip to main content
Glama

FilingDesk Data

by com.filingdesk

Compare state or entity-type options

compare_formation_options
Read-only

Factual tradeoffs to help someone decide WHERE to form or WHAT entity type to pick. Returns fixed comparative facts and a required disclaimer — deliberately NOT a recommendation. Present the options neutrally, relay the disclaimer, and let the user choose; a FilingDesk specialist confirms the choice before anything is filed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYes"state" for where to form, "entity_type" for LLC vs S-corp vs C-corp.
homeStateNoOptional. The state the user actually lives or operates in — lets the comparison include their home-state costs, which usually matter most.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only provide readOnlyHint=true, but the description adds critical behavioral guidance: returns fixed comparative facts, includes a required disclaimer, must be presented neutrally, and a human specialist confirms before filing. This goes well beyond the annotation.

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 main purpose and followed by actionable usage instructions. No fluff or repetition; every sentence earns its place.

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?

With no output schema, the description adequately conveys return type (fixed comparative facts and disclaimer) and the overall process (neutral presentation, specialist confirmation). Combined with good schema descriptions and readOnly annotation, the description is complete for this decision-support 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% and both parameters are well-described in the schema (topic enum with meanings, homeState with what it does). The tool description itself adds no additional parameter semantics, so 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?

Description clearly states the tool's purpose: to provide factual tradeoffs for deciding where to form or what entity type to pick. It distinguishes itself from siblings like compare_llc_costs by covering both state and entity type options, not just costs.

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 says when to use: when someone needs to decide WHERE to form or WHAT entity type to pick. It also gives when-not: deliberately NOT a recommendation, and that FilingDesk specialist confirms before filing, setting clear boundaries and usage context.

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
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