Skip to main content
Glama

Formation Lane US LLC Fees & Deadlines

LLC formation fees for a state

get_state_llc_fees
Read-onlyIdempotent

State fee to form a domestic LLC in one US state or DC, plus the recurring report fee, franchise/privilege tax note, state-specific caveats, the official state filing office URL, official source URLs, Formation Lane's guide URL, and the last_checked date.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "get_state_llc_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesUS state or DC: full name ("Georgia") or two-letter postal code ("GA").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds useful transparency about the returned data, including recurring report fees, caveats, official source URLs, and a last_checked date, but it does not discuss freshness policy, caching, or error behavior. With annotations covering the safety profile, this is roughly adequate but not rich.

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 definition is a single dense sentence with the core fee purpose front-loaded and the returned fields listed afterward. It is efficient and avoids repetition, though the long list makes it slightly run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the burden of explaining return content, and it enumerates the major returned fields clearly. For a simple one-parameter lookup with annotations, it is nearly complete, though it could briefly state behavior for invalid or unsupported state values.

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 the schema already documents that the state parameter accepts a full state name or two-letter postal code. The description reinforces 'one US state or DC' but adds no formatting, validation, or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: the fee to form a domestic LLC in one US state or DC. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as get_annual_report or list_states.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The definition provides no explicit when-to-use guidance, no alternatives, and no prerequisites. A reader can infer it is a state lookup, but the description does not say when to choose it over related tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources