Skip to main content
Glama

get_notes_of_decisions

Retrieve annotated notes of decisions for a statute, court rule, constitutional provision, or admin-code section, showing citing opinions, cited subsections, and treatment signals.

Instructions

Annotated "Notes of Decisions" for a statute, court rule, constitutional provision, or admin-code section: every citing opinion with its citing sentences (verbatim, with ¶ pinpoints), the SUBSECTION each mention cites, and depth-of-treatment signals — a research view of how courts have applied the provision, grouped and ranked (vs find_opinions_construing's bare list).

Per citing opinion: mentions (in-text occurrence count), construes (interpretive vocabulary near a mention — heuristic), quotes_provision (reproduces ≥8 consecutive words of the provision's text), subsections_cited (parsed pinpoints, oracle-validated against the provision's structured subsection index where available), the opinion's own cited-by count, and the provision VERSION in force when it was filed (for an N.D.C.C. section, construed_version: 'current' / 'earlier' / 'unknown', from the date the current text took effect). The header aggregates a per-subsection citation outline and the provision's amendment timeline, so notes can be read against text changes.

Signals are heuristic and NON-authoritative — read the returned context (and the full opinion) before relying on any of them.

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": {
      "authority": "<authority>"
    },
    "name": "get_notes_of_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries returned per call (default 20, max 100).
orderNo"weight" (construes > quotes > mentions > cited-by > recency), "recency", or "depth" (mention count).weight
offsetNoPagination offset into the ordered entry list.
date_toNoOptional ISO date — only opinions filed on/before.
authorityYese.g. "N.D.C.C. § 14-09-06.2", "N.D.R.Civ.P. 56", "N.D. Const. art. I, § 8", "N.D.A.C. § 75-02-04.1-02".
date_fromNoOptional ISO date — only opinions filed on/after.
scan_limitNoMax (most-recent) citing opinions scanned (default 300); aggregates cover the scanned set.
subsectionNoOptional pinpoint filter, e.g. "(1)(j)" — only opinions whose mentions cite that subsection (or a child of it).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses that signals are heuristic and NON-authoritative, that subsection parsing is oracle-validated only where a structured index exists, and that scan_limit bounds the scanned set so aggregates cover only that set — a material caveat an agent would otherwise miss. It also explains version-in-force semantics (construed_version from the effective date of current text).

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 lead sentence is front-loaded with purpose and the sibling contrast, and the caveat about heuristics closes it cleanly. The middle field-by-field glossary is dense and useful but partly duplicates what an output schema (present) already provides, making it slightly longer than necessary.

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 an 8-parameter, no-annotation tool this covers the essentials: what is returned, how ranking and scanning bound the results, and how much trust to place in the heuristics. Since an output schema exists, the detailed return-value glossary is a bonus rather than a requirement, and the only real gap is guidance on obtaining or validating the required authority string.

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%, including the weight formula for order, scan_limit's aggregation caveat, and the subsection pinpoint format, so the schema already does the heavy lifting. The prose adds output-field semantics (mentions, construes, quotes_provision, subsections_cited) rather than meaning for the input parameters, so it lands at the baseline.

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 (annotated Notes of Decisions for a statute/rule/constitutional provision/admin-code section) and a specific shape of output (every citing opinion with citing sentences, subsection pinpoints, depth signals). It also explicitly positions itself against the sibling find_opinions_construing ("vs find_opinions_construing's bare list"), so an agent can discriminate without opening either schema.

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

Usage Guidelines4/5

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

It gives a clear selection cue: use this for a grouped/ranked research view of how courts applied a provision, and use find_opinions_construing when a bare list suffices. It does not state explicit exclusions or prerequisites (e.g. whether the authority string must already be verified via verify_citation/lookup_authority), so it stops short of full when/when-not guidance.

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