Skip to main content
Glama

NY LLC Publication (FileMyPublication)

Draft the publication notice

draft_publication_notice
Read-onlyIdempotent

Drafts the legal notice text a New York LLC publishes (§206), a foreign LLC's Notice of Qualification (§802), or a PLLC's notice (§1203), from the LLC's details. Anything not given prints as a bracketed placeholder. Uses the same wording the FileMyPublication site generates.

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": {
      "llc_name": "<llc_name>"
    },
    "name": "draft_publication_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNoThe New York county named in the LLC's Articles of Organization, e.g. 'Albany', 'Nassau', 'Brooklyn' or 'Kings'. Borough names are accepted.
purposeNoBusiness purpose. Leave out for 'any lawful act'. For a PLLC, the profession.
llc_nameYesThe LLC's exact name as filed with the Department of State.
llc_typeNoDefaults to llc.
formation_dateNoFiling date of the Articles of Organization (foreign LLC: Application for Authority), YYYY-MM-DD.
foreign_jurisdictionNoForeign LLC only: state or country of organization.
registered_agent_nameNoOptional registered agent's name (with its address).
foreign_formation_dateNoForeign LLC only: date of organization, YYYY-MM-DD.
foreign_office_addressNoForeign LLC only: office address in the home jurisdiction.
registered_agent_addressNoOptional registered agent's address.
principal_business_addressNoOptional §206(a)(3-a) principal business location.
service_of_process_addressNoThe address the Secretary of State mails legal papers to, from the filing receipt.

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 establish readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is to add operational detail — and it does: missing inputs become bracketed placeholders rather than errors, and output wording mirrors the FileMyPublication site. What it omits is the output shape (plain text block? formatted document?) and whether the draft is safe to reuse verbatim for filing.

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, zero filler: the first front-loads what is produced and for which entity types, the second covers placeholder behavior and wording fidelity. The statutory citations earn their space by disambiguating the three variants.

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 12-parameter generator with no output schema and a fully documented input schema, the description covers purpose, entity variants, partial-input behavior, and wording source. The remaining gap is the return format and whether the generated text is a final filing-ready notice, which an agent would want before passing it downstream.

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%, so per-parameter meaning is already fully documented and the baseline applies. The description contributes one genuinely useful semantic beyond the schema: omitted fields render as bracketed placeholders, which explains why 11 of 12 parameters are optional and how partial input is handled. That is real added value but limited to a single behavioral rule.

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?

States a specific verb ('Drafts') and resource ('legal notice text') and enumerates the three statutory variants it covers (§206 LLC, §802 foreign LLC, §1203 PLLC), plus the source of the input ('the LLC's details'). This is clearly separable from siblings like get_publication_requirements, get_county_publication_cost, or start_order, which handle requirements, pricing, and ordering rather than text generation.

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 statute-per-entity-type framing tells the agent which case each draft applies to, and the 'from the LLC's details' phrasing implies it is a generation step rather than a lookup or filing step. It stops short of explicit when-not guidance (e.g., 'call get_publication_requirements first' or 'this does not file or place the notice'), so the routing to siblings is inferred rather than stated.

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