Rettsarkiv

Søk i avgjørelser

search_decisions

Read-only

Fritekstsøk i norske Høyesteretts-avgjørelser — rangerte treff, klare til å presenteres direkte. Hver rad: primary_id, decision_date, summary, sitering_count. Oppgi lov+section for å begrense til dommer som anvender en bestemt paragraf (samme utgave-bevisste nøkkel som find_decisions_applying_law). court_level (instans-filter) tar hoyesterett | lagmannsrett | tingrett (aliasene «HR»/«Høyesterett» godtas også); utelat for alle instanser. Hent fulltekst for en konkret dom via get_decision. Svar med lista.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	Yes
`lov`	No
`limit`	No
`on_date`	No
`section`	No
`to_date`	No
`from_date`	No
`court_level`	No
`decision_type`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJun 9, 2026

addedInput schema / properties / on_date

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "On Date"
+}

First observedJun 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The description lists output fields and states that results are ranked, which adds some behavioral insight. However, it does not disclose pagination behavior or rate limits. Since annotations already indicate readOnlyHint=true, the additional disclosure is moderate but not extensive.

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 a single paragraph but efficiently packs purpose, parameter details, and sibling reference. It is well-structured with front-loaded purpose, though slightly dense. Could benefit from bullet points but remains concise.

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?

Given 9 parameters, no output schema, and complexity, the description covers primary purpose, output format, parameter usage, and related tools. It lacks explicit pagination details but is otherwise complete for an agent to use effectively.

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

Parameters4/5

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

The description adds meaning to many parameters (lov, section, court_level with aliases, date range) beyond the schema titles. However, decision_type is not explained. With 0% schema description coverage, the description compensates well for most parameters.

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 clearly states that the tool performs free-text search on Norwegian Supreme Court decisions, returning ranked results with specific fields. It distinguishes itself from sibling tools like find_decisions_applying_law and get_decision.

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 guidance on when to use this tool (for free-text search) and explains how to filter by parameters like lov, section, court_level with aliases. It also directs users to get_decision for full text, clarifying alternatives.

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

All Rettsarkiv tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?