Skip to main content
Glama

cpl_lookup_section

Read-onlyIdempotent

Retrieve the full official text of a specific New York Criminal Procedure Law (CPL) section by entering its citation. Get the statute, section title, and structural context in one response.

Instructions

Retrieve the full text of a single New York Criminal Procedure Law (CPL) location by citation.

Use this when the user names a specific CPL section or article (e.g. "What does CPL 245.20 say?", "pull up CPL section 510.10"). It returns the official statute text plus its title and structural context (article/title parents and adjacent sections). It does NOT search by topic — use cpl_search for that.

Args: params (LookupInput): Validated input containing: - citation (str): A CPL location id such as "245.20", "1.20", "A245", or "T1". Leading "CPL", "section", and "§" are stripped automatically. - response_format (ResponseFormat): "markdown" (default) or "json".

Returns: str: In markdown mode, a formatted document with the section title, citation, full statute text, structural breadcrumb, and a source link. In json mode, an object with this schema: { "lawId": str, # "CPL" "locationId": str, # e.g. "245.20" "docType": str, # e.g. "SECTION", "ARTICLE", "TITLE" "title": str, # human title, e.g. "Automatic discovery" "activeDate": str, # ISO date this version became active "text": str, # full statute text "parents": [ {"docType": str, "docLevelId": str, "title": str} ], "sourceUrl": str # canonical nysenate.gov page }

On failure, a string beginning with "Error:".

Examples: - Use when: "Show me CPL 245.20" -> citation="245.20" - Use when: "What's in article 245 of the CPL?" -> citation="A245" - Don't use when: "Which CPL section covers discovery?" (use cpl_search instead)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond this: input normalization ('Leading "CPL", "section", and "§" are stripped automatically'), return format details (markdown vs. json with full object schema), and error behavior ('On failure, a string beginning with "Error:"'). No contradiction with annotations.

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?

The description is well-structured with a clear lead sentence, separate Args, Returns, and Examples sections. It is fairly long but every section provides necessary information for correct tool usage; it only slightly duplicates schema details.

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

Completeness5/5

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

The description is fully self-contained: it covers input normalization, output format, return schema, error handling, and differentiation from the sibling tool. Given the tool's moderate complexity and the presence of an output schema, the description leaves no gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema includes detailed descriptions for both parameters, the description reinforces and clarifies them with concrete examples of valid citations ('245.20', 'A245', 'T1') and the expected response_format values. It also explains the output schema in plain language, which goes beyond the schema's field descriptors.

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 opens with a specific verb ('Retrieve') and resource ('full text of a single New York Criminal Procedure Law location by citation'), making the tool's exact function clear. It also explicitly distinguishes itself from the sibling tool cpl_search by stating 'It does NOT search by topic — use cpl_search for that.'

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance ('Use this when the user names a specific CPL section or article'), when-not-to-use ('Don't use when: 'Which CPL section covers discovery?''), and names the alternative tool (cpl_search). It also includes concrete examples of user utterances and corresponding citation values.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/njrenaissance/cpl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server