Skip to main content
Glama

NY LLC Publication (FileMyPublication)

County Clerk contact details

get_county_clerk
Read-onlyIdempotent

The County Clerk's office for a New York county: phone, address, hours, email and website. The Clerk designates the newspapers an LLC must publish in.

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

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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine domain context — that the Clerk designates the newspapers an LLC must publish in — but says nothing about what happens for an unrecognized county or whether results are cached/stale.

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 short sentences with no waste; the returned fields come first and the domain-relevant newspaper fact second. Nothing is padded or repeated from the title.

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?

With no output schema, the description appropriately compensates by listing the returned fields. For a one-parameter read tool this is nearly complete; only the error/empty-result behavior for an unknown or non-New-York county is left unstated.

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%, and the schema already explains that borough names are accepted for the county parameter. The description adds no additional meaning about the single required parameter, so the baseline of 3 applies.

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?

The description names a specific resource (the County Clerk's office for a New York county) and enumerates what it returns: phone, address, hours, email and website. It also states a second, distinct fact the tool surfaces — which newspapers the Clerk designates — which separates it from county-related siblings like get_county_publication_cost.

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 only implied: an agent can infer this is the tool for contact details or for determining designated newspapers, but the description never says when to prefer it over get_county_publication_cost or get_publication_requirements. No exclusions or prerequisites are given.

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