Skip to main content
Glama

Formation Lane US LLC Fees & Deadlines

LLC annual report: fee, due date, late penalty

get_annual_report
Read-onlyIdempotent

Recurring state report for a domestic LLC in one US state or DC: report name (annual, biennial, or none), filing fee, due date or rule, late penalty, any franchise/privilege tax, the official state filing URL, Formation Lane's annual-report 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_annual_report"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description needn't repeat it. It adds useful behavioral context by disclosing the full return payload and, notably, a last_checked freshness field, which tells the agent the data is cached and may be dated. It stops short of explaining how stale data is handled or what is returned for a state with no report requirement.

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?

A single tightly packed sentence that front-loads the resource and scope before listing outputs; every clause maps to a real returned field, so nothing is filler. The long inline enumeration makes it list-heavy but not wasteful.

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 correctly compensates by enumerating the returned fields, and it even notes that report name may be 'none,' covering the no-requirement case. For a one-parameter read tool with annotations in place this is nearly complete; only unsupported-state handling is unaddressed.

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 single 'state' parameter already documents both full-name and postal-code formats, so the schema does the heavy lifting. The description only reinforces the one-state scope ('in one US state or DC') without adding syntax or validation detail beyond the schema, matching the baseline 3 for high coverage.

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 names a specific resource (recurring state annual/biennial report requirements for a domestic LLC) and enumerates the exact fields returned: report name, filing fee, due date/rule, late penalty, franchise/privilege tax, filing URL, guide URL, last_checked. It does not, however, distinguish itself from the sibling get_state_llc_fees, so an agent cannot tell purely from this text which one to call for fee questions.

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

Usage Guidelines3/5

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

Scope is implied by 'domestic LLC' and 'recurring state report,' which suggests ongoing compliance rather than initial formation, but there is no explicit when-to-use/when-not guidance and no alternative tool is named. The agent must infer the boundary with get_state_llc_fees on its own.

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