Skip to main content
Glama

NY LLC Publication (FileMyPublication)

New York LLC publication requirements

get_publication_requirements
Read-onlyIdempotent

Explains New York's LLC publication requirement: LLC Law §206 for New York LLCs, §802 for out-of-state (foreign) LLCs registered in New York, and §1203 for PLLCs. Covers the two newspapers, six weeks, the 120-day deadline, the Certificate of Publication and what happens if it is missed.

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_publication_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
llc_typeNollc = formed in New York (default); foreign_llc = formed in another state and registered in New York; pllc = professional LLC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds substantive scope context (statutes, two newspapers, six weeks, 120-day deadline, Certificate of Publication, missed-deadline consequences) but says nothing about the form of the answer or its length. Useful added context, not rich behavioral disclosure.

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?

A single front-loaded sentence organized by statute, then by the practical elements covered (newspapers, timeline, certificate, failure). Every clause carries distinct information and there is no filler.

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 simple read-only explainer with one optional enum parameter and no output schema, the topic coverage is thorough enough to call it correctly. The remaining gap is routing guidance relative to the deadline/cost/order siblings, which would make it fully self-sufficient.

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?

Schema coverage is 100%, so baseline is 3, but the description earns more by mapping each enum value to a concrete outcome (llc → §206, foreign_llc → §802, pllc → §1203). That tells the agent what it gets per input, which the schema only partially conveys via enum labels.

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?

Opens with a specific verb+resource ("Explains New York's LLC publication requirement") and enumerates the exact statutory coverage, which makes its informational role distinguishable from the calculator/cost siblings. It never names a sibling or explicitly contrasts itself, so it stops short of full differentiation.

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?

No explicit when-to-use, when-not-to-use, or alternative routing is stated; the agent must infer that this is the reference/explainer tool to consult before using calculate_publication_deadline, get_county_publication_cost, or start_order. The implied usage is clear from the enumerated scope, but nothing is spelled out.

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