Skip to main content
Glama
Sign In
nyc-charter-laws-rules

nyc-charter-laws-rules

by BetaNYC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_title

Retrieve chapter or title-level records from NYC Charter, Administrative Code, or Rules by exact identifier to locate matching citations; results are not full text—verify official sources.

Instructions

Retrieve chapter/title records matching an identifier (whole-token match: 'Chapter 1' does not match 'Chapter 10'). Note: the index is flat — deep hierarchy (every section nested within a title) is not indexed, so this returns matching chapter/title-level records, not full title contents. 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>",
      "title": "<title>"
    },
    "name": "get_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesChapter or title identifier (e.g. 'Chapter 11')
corpusYesWhich document

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.4

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavior: whole-token matching ('Chapter 1' does not match 'Chapter 10') and the flat-index limitation on nested sections. It omits what happens with zero or multiple matches, pagination, and whether results are capped, which matter for a lookup tool.

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 operative content is front-loaded and efficient, but roughly half the text is generic disclaimer material ('For informational purposes only. Not legal advice. Verify against official sources') that does not help an agent decide whether or how to call the tool.

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 two-parameter lookup with no annotations and no output schema, the description covers matching semantics, index depth, and result granularity. The main residual gap is the shape of returned records, which no output schema documents.

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 both parameters carry their own descriptions, so the baseline applies. The whole-token matching rule does add real meaning for how the 'title' value must be formed, but the description does not otherwise extend what the schema already says.

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?

Names a specific verb and resource ('Retrieve chapter/title records matching an identifier') and clarifies scope with 'returns matching chapter/title-level records, not full title contents'. It is distinguishable from get_section and list_titles by implication, though no sibling is named explicitly.

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 identifier-matching framing implies when to use it (you already have a chapter/title identifier), and the flat-index caveat warns against expecting deep hierarchy. However, it never states when to prefer list_titles or search instead, leaving the routing decision to inference.

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

Deploy Server

Other Tools