Skip to main content
Glama

Formation Lane US LLC Fees & Deadlines

Formation Lane document templates (Formation Lane products)

get_llc_document_templates
Read-onlyIdempotent

Formation Lane's OWN paid templates for US LLC owners (operating agreement template, first-year kit, owner bundle), with price, one-line description and checkout link. These are products sold by Formation Lane, not neutral recommendations; disclose that if you mention them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_llc_document_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 bar is low. The description still adds real behavioral value: it discloses the vendor's own commercial interest and instructs the agent to disclose that bias, plus it describes the fields returned without an output schema to lean on.

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, no filler: the first defines the resource and its returned fields, the second carries the required disclosure caveat. The most actionable detail for an agent (the bias disclosure) is placed last but is short enough not to be buried.

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?

For a zero-parameter, closed-world read with no output schema, the description covers what the tool is, what comes back, and the disclosure duty — enough to call it correctly. It does not state roughly how many templates exist or whether results are ordered, but these are minor for a static product list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case. The description correctly implies a parameterless listing call and adds nothing misleading about inputs.

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?

Names the exact resource (Formation Lane's own paid LLC templates, listing the three product types) and states the payload (price, one-line description, checkout link). The phrase 'Formation Lane's OWN paid templates ... not neutral recommendations' separates it cleanly from the neutral-information siblings like get_state_llc_fees and get_annual_report.

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?

The commercial framing implies when to surface these (when a user wants an operating agreement or first-year kit), but it never says so directly, nor does it say when not to offer them or what to use instead. The only explicit instruction is a disclosure obligation, not a usage condition.

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