Skip to main content
Glama

NY LLC Publication (FileMyPublication)

LLC publication cost by county

get_county_publication_cost
Read-onlyIdempotent

FileMyPublication's all-in price to complete New York LLC publication in a county (both newspapers for six weeks, the State filing fee and our service fee) and the newspapers designated there. In Manhattan, Brooklyn, Queens and the Bronx the County Clerk assigns the papers, so the price is quoted once the Clerk names them.

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": {
      "county": "<county>"
    },
    "name": "get_county_publication_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyYesThe New York county named in the LLC's Articles of Organization, e.g. 'Albany', 'Nassau', 'Brooklyn' or 'Kings'. Borough names are accepted.

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?

Beyond the readOnly/idempotent annotations, the description discloses what the quoted figure actually covers (both newspapers for six weeks, State filing fee, service fee) and warns that in Manhattan, Brooklyn, Queens and the Bronx the price is not available until the County Clerk assigns papers. That is substantive behavioral context an agent could not infer from the annotations. It says nothing about response shape when the price is pending, which keeps it off a 5.

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?

Two sentences, both earning their place, with the price definition front-loaded and the exception following. Punctuation and clause stacking are dense in the first sentence, but nothing is redundant.

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 tool with no output schema, the description covers what the price represents and mentions the second return element (designated newspapers). The one unresolved point is what an agent receives when the Clerk has not yet named papers, but the conditional nature is at least signalled.

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 county field already documents accepted forms, including borough names. The description reinforces this by naming Manhattan, Brooklyn, Queens and the Bronx as borough inputs that behave differently, but adds no syntax or normalization detail beyond the schema, so the baseline 3 applies.

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 and verb: the all-in price to complete New York LLC publication in a given county, plus the newspapers designated there. It is clearly distinct from siblings like get_county_clerk or get_publication_requirements, but it never explicitly routes the agent away from those tools, so it stops short of a 5.

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?

Usage is implied — you call it when you need a county's publication price — and the description does flag the conditional case where no price exists yet (the NYC boroughs). It gives no explicit when-not guidance and never mentions alternatives such as get_publication_requirements or start_order.

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