nyc-charter-laws-rules

list_titles

Lists top-level chapters or titles for a chosen NYC Charter, Administrative Code, or Rules document, helping users identify sections to browse or cite.

Instructions

List the top-level chapters or titles of a document. For informational purposes only. Not legal advice. Verify against official sources at codelibrary.amlegal.com before relying on any result.

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": {
      "corpus": "<corpus>"
    },
    "name": "list_titles"
  }
}

Input Schema

Name	Required	Description	Default
`corpus`	Yes	Which document to list

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.4Nov 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It says nothing about what the listing contains (bare titles vs. identifiers), whether the result is paginated, or whether it is a safe read-only operation. The 'verify against official sources' caveat adds a modest accuracy warning but not operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, which is good. However, roughly half the text is boilerplate disclaimer wording that does not help an agent select or invoke the tool, so not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter read tool with no output schema, so the description need not explain much. Still, with no output schema, a hint about the shape of the returned list (strings, entries with section counts) would materially help the agent. The definition is adequate but leaves that gap.

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?

There is one required parameter, corpus, and the schema documents it fully at 100% coverage with an enum of charter/admin_code/rules. The phrase 'of a document' in the description loosely maps to that selector but adds no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb and resource: 'List the top-level chapters or titles of a document.' That is enough to distinguish it from get_section, get_title, and search, which operate on narrower or different resources. It stops short of explicitly naming a sibling, so it is clear but not maximally differentiated.

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?

No when-to-use or when-not-to-use guidance is given. The remaining sentences are legal disclaimers ('For informational purposes only. Not legal advice.') and a verification instruction, which tell the agent about liability, not about which tool or corpus to pick. An agent gets no help choosing list_titles over get_title for a given task.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server