Skip to main content
Glama

NY LLC Publication (FileMyPublication)

FileMyPublication services and prices

list_llc_services
Read-onlyIdempotent

FileMyPublication's New York LLC services with their all-in prices: LLC publication, filing the Certificate of Publication, Certificate of Change, Articles of Dissolution and a certified copy of the Articles of Organization.

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": "list_llc_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds scope (New York LLC only) and implies a static catalog with no side effects, but says nothing about return shape, currency, or whether prices are live.

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?

A single sentence with the scope ('New York LLC services with their all-in prices') front-loaded before the enumeration. The service list is long but each item is informative content rather than filler; a slightly tighter phrasing would earn a 5.

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, read-only catalog tool with rich annotations, the description is close to complete: it tells the agent what categories of services and prices come back. The remaining gap is that no output schema exists and the description does not describe the return structure (list vs. table, price format).

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, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter information is missing or misleading.

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 the specific resource (New York LLC services and their all-in prices) and enumerates exactly which services are covered, so an agent knows what a call returns. It does not, however, distinguish this tool from siblings like get_county_publication_cost, which also concerns pricing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no mention of alternatives such as get_county_publication_cost for county-level pricing or start_order for purchasing. The intended use (browse the catalog before ordering) is only inferable from the phrase 'all-in prices'.

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