Skip to main content
Glama

FilingDesk Data

by com.filingdesk

Check business-name availability

check_llc_name
Read-only

Check a proposed business name against a state's live registry. REAL results for Wyoming and Delaware only; Florida returns a Sunbiz search link; all other states return unsupported. A verdict is an indication, never a reservation — always show the returned note and verifyUrl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe proposed name, e.g. "Blue Harbor Holdings LLC".
stateYesState code or name. Live checks: "WY", "DE". Link-only: "FL".
entityTypeNoDefaults to llc.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that a verdict is an indication, never a reservation, and that the note and verifyUrl must be shown. It also explains state-specific behaviors, adding meaningful context for the agent without contradicting annotations.

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?

The description is two sentences, front-loaded with purpose, then concise caveats about state coverage and legal status. Every word 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?

For a simple lookup tool with no output schema, the description fully explains state-specific outcomes, what to return, and the non-reservation caveat. It covers all necessary context for correct invocation and response handling.

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%, so the baseline is 3. The description adds no extra parameter meaning beyond what the schema already documents; it only references state behavior in prose.

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 checks a proposed business name against a state's live registry, which is a specific verb+resource. It distinguishes from siblings by focusing on name availability, not formation, fees, or deadlines.

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?

The description gives clear context on state support (real results for WY/DE, Florida link-only, others unsupported) and instructs to always show the returned note and verifyUrl. It does not explicitly name alternatives, but none of the sibling tools offer this functionality.

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