Skip to main content
Glama

NY LLC Publication (FileMyPublication)

120-day publication deadline

calculate_publication_deadline
Read-onlyIdempotent

Calculates a New York LLC's publication deadline: 120 days from the date its Articles of Organization were filed (or, for a foreign LLC, from when its Application for Authority took effect). Returns the date and the days remaining.

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": {
      "formation_date": "<formation_date>"
    },
    "name": "calculate_publication_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
formation_dateYesFiling date of the Articles of Organization, YYYY-MM-DD.

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds real value beyond them by disclosing the computation rule, the foreign-LLC starting-point variant, and the return contents (deadline date plus days remaining). It stops short of describing what happens when the deadline has already passed, which is the main remaining behavioral gap.

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: the first front-loads the rule with the foreign-LLC exception parenthetically, the second states the return value. Every clause carries 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 single-parameter, read-only calculation with no output schema, the description covers the input interpretation, the computation rule, and the shape of the result. The only shortfall is undefined behavior for already-expired or future-dated inputs, a minor edge case for a deterministic calculator.

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 would be 3; the description earns an extra point by clarifying that formation_date drives the calculation for both domestic and foreign entities, extending the schema's terse 'filing date' note. It does not add format details, but the schema already supplies YYYY-MM-DD.

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 (calculates) and a precise resource (a New York LLC's 120-day publication deadline), and spells out the exact rule: 120 days from the Articles of Organization filing date, or from the effective date of the Application for Authority for a foreign LLC. This is unambiguous and clearly distinct from siblings like draft_publication_notice or get_publication_requirements.

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 narrow scope implies when to use it (a user asking how long they have to publish), and the foreign-LLC clause tells the agent which date to supply. However, there is no explicit statement of when NOT to use it or a named alternative for adjacent needs (e.g., requirements or county costs), so guidance is implied 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