ndlaw

Overview Schema Source Related Servers Discussions Admin

search_boolean

Run Boolean and proximity searches over North Dakota court opinions to find terms using AND, OR, NOT, /N, /s, /p, truncation, and quoted phrases.

Instructions

Terms-and-connectors Boolean / proximity search.

Connectors: & (AND), | or OR (OR), % or NOT (BUT NOT), /N (within N words), /s (same sentence ≈ NEAR/20), /p (same paragraph ≈ NEAR/50), ! truncation (e.g. negligen! → negligen*), and "quoted phrases". Because FTS5 has no sentence/paragraph unit, /s and /p are token-distance approximations — the translated FTS query and any approximation notes are returned for transparency.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results (default 20, max 50).
`query`	Yes	A terms-and-connectors query (e.g. `warrant /s nighttime % consent`).
`author`	No	Filter by authoring justice's last name.
`date_to`	No	Filter to opinions filed on/before this date (YYYY-MM-DD).
`date_from`	No	Filter to opinions filed on/after this date (YYYY-MM-DD).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.4.2Sep 11, 2026

changedInput schema / properties / query / description

Previous value: -"A Westlaw-style query (e.g. `warrant /s nighttime % consent`)."New value: +"A terms-and-connectors query (e.g. `warrant /s nighttime % consent`)."

First observedv3.4.0Aug 31, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that /s and /p are token-distance approximations and that the translated FTS query and approximation notes are returned for transparency, which are important behavioral traits beyond the schema.

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 front-loaded with the tool's mechanism and then lists connector details efficiently. It is dense but every sentence supports query construction, with no obvious filler.

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?

Given the complexity of Boolean search syntax, the description is fairly complete for invocation. However, with many sibling search tools available and an output schema present, it omits what corpus is searched and when to prefer this tool over alternatives, leaving a clear selection gap.

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 schema description coverage is 100%, the description adds substantial meaning beyond the schema by documenting the connector syntax, truncation, and proximity operators for the query parameter. This is essential semantic detail that the schema alone does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is a 'Terms-and-connectors Boolean / proximity search', which identifies the search mechanism but not the corpus being searched. Sibling tools include several search variants (e.g. search_opinions, search_faceted), and this description does not differentiate itself from them.

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?

The description explains connector syntax but provides no guidance on when to choose this tool over sibling search tools. There is no mention of prerequisites, alternatives, or when-not-to-use conditions.

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

Deploy Server