Skip to main content
Glama

Resolve Austrian Legal Citation

ris_lookup_citation
Read-onlyIdempotent

Resolve a single Austrian legal citation to its canonical RIS document deterministically — no keyword search. Four routes are auto-detected from the citation shape (or forced with kind): a norm citation — section-first ("§ 6 DSG", "Art 10 B-VG"), abbreviation-first ("DSG §1", "EMRK Art8", the shape ris_search_case_law returns in norms_cited; a comma-joined entry like "DSG §1, §24", or one joining full norms with ". " like "ZPO §179. ZPO §275 Abs2", resolves its first provision and names the rest), or a bare abbreviation like "ABGB" or "1. COVID-19-JuBG", with sub-provisions (Abs, Z, lit, "(1)"), the version a law is cited in ("ABGB idF 2. ErwSchG §254", "ABGB aF §140"), and a terminal ";" dropped, and a long title read by its short form after the dash ("StaatsanwaltschaftsG - StAG §35") — resolves through consolidated federal law, or a Bundesland with a state hint, as in force today or on in_force_as_of, while an EU act RIS does not consolidate (DSGVO, the Charter, EuGVVO, the EC Treaty as EG, EGV, or EG-Vertrag), or an EU act cited by its number ("RL 2006/123/EG", "VO (EG) 178/2002"), returns found: false pointing to EUR-Lex without a search; a gazette citation ("BGBl. I Nr. 165/1999", year-first "BGBl I 2018/24", pre-2004 "BGBl. Nr. 194/1961", imperial "RGBl. Nr. 189/1902", "StGBl. Nr. 1/1945", or "LGBl. Nr. 61/2026" with a state hint) routes to the right federal era tier by year — the 1945 Staatsgesetzblatt sits in the 1945–2003 tier beside the BGBl. — or to a state Landesgesetzblatt — falling back to that Bundesland’s pre-e-Recht series when the citation predates its switch — and a string of several cites, as a consolidated record’s promulgation joins them ("BGBl. Nr. 267/1967 zuletzt geändert durch BGBl. I Nr. 17/2026"), resolves by its first cite alone, its prefix, part, and number read from that cite, and names each later cite with its linking words without searching it, while a first cite in a gazette this lookup does not read ("ABl.Nr. 52/2006 …") returns found: false without a search; a case number ("Ro 2026/03/0016", "G 287/2022", "14Os49/26a", "2025-0.934.677", "W256 …") is matched to its court — a leading VfGH, VwGH, OGH, BVwG, or DSB names it ("VfGH G 13/2025"), court skips detection, and ambiguous formats probe up to two courts; an ECLI ("ECLI:AT:VFGH:2026:G13.2025") resolves to the decision that carries it; a Justiz Rechtssatz number — RS for an OGH headnote ("RS0022961", "RIS-Justiz RS0022961 [T3, T7]"), an OLG’s or LG’s own prefix for theirs ("RW0001127") — resolves to that headnote through Justiz whatever the court hint, its bracketed T numbers (Beisätze inside the same Rechtssatz) not searched; a collection number ("VfSlg 19.632/2012", "VwSlg 18.000 A/2010") resolves through the VfGH/VwGH collection to a decision of the year cited, matched against its decision year or, on VwGH, also the year its Sammlungsnummer carries (a two-digit year compares on its last two digits); a VwSlg cite with a year whose first search finds no decision of that year is searched once more as "1485" within that year’s decision dates (a two-digit year spans the latest year ending in it), which reaches the other shapes VwGH stores older cites in ("VwSlg 0017 F/1947", "VwSlg. 1485 A/1950", "VwSlg 10414/A"), taking only a row that names the cited number, a part letter not contradicting the cited one, and the year; a number that matched only other years, or on that second search only rows under another part letter, comes back as found: false naming each cite it does match, and a cite naming more than one decision — a VwSlg cite without its part letter (the A and F series reuse numbers), or a VfSlg number from the 1919–1920 volumes without its year (VfSlg numbering restarted in 1921) — comes back as ambiguous with each cite named rather than resolved to one of them. Matches are ranked before one is picked: a norm resolves to the hit whose abbreviation is the cited one, then the cited one plus a year ("EStG" → EStG 1988), then the cited one without a year RIS’s abbreviation omits, when the law’s short title carries it ("AlVG 1977" → AlVG), the exact §/Artikel label ahead of a prefixed one ("§ 1" before "Art. 2 § 1"), and a cite whose year matches nothing ("VwGVG 2014 §28") is searched once more without it, taking only the law filed under the cited abbreviation without that year and first promulgated no later than it ("VwGVG 2014" → VwGVG, not "AVG 1950" → the AVG of 1991), for a year no later than in_force_as_of’s; a case number resolves to the decision text, then to a Rechtssatz that decision leads; a gazette cite resolves only to an entry of the gazette it names (StGBl. and BGBl. share numbers in 1945, as the older gazettes do in their changeover years); and a "BGBl. Nr." cite without its part that matches more than one of parts I/II/III (from 1997 they reuse numbers) comes back as ambiguous with each part named. An RIS ELI link — the eli or document_url a consolidated-law or authentic-gazette record carries ("https://www.ris.bka.gv.at/eli/bgbl/1974/60/P75/NOR12029618", "https://www.ris.bka.gv.at/eli/bgbl/II/2026/317/20261103") — is read first under kind auto, before any cite shape: a consolidated provision’s ELI resolves as a norm to the provision whose document number it ends in, in force or not, with in_force_as_of and state not applied, and an authentic gazette’s ELI resolves as a gazette to the entry it names; an /eli/ path in another layout that spells a gazette cite (/eli/bgbl/{I|II|III}/{year}/{number}, /eli/lgbl/{state}/{year}/{number}, or /eli/{bgbl|rgbl|stgbl|gbloe}/{year}/{number} with no part, as before 1997) followed by nothing but date, language, or format segments ("/eli/bgbl/II/2026/317", "/eli/bgbl/1974/60") is classified as that cite, and any other /eli/ layout, such as a provision’s path cut before its document number, returns found: false with kind unknown, nothing searched. Returns the single best-matching document in the same shape as the corresponding search tool, with alternatives_count when more than one matched. A citation that cannot be classified or resolved returns found: false with next-step guidance — it never throws for a miss; only an upstream RIS outage is an error. For keyword rather than citation lookup, use ris_search_legislation or ris_search_case_law.

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": {
      "citation": "<citation>"
    },
    "name": "ris_lookup_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoForce a route, or auto (default) to classify by shape; only auto reads an RIS ELI link. Set explicitly when the citation shape is ambiguous.auto
courtNoCourt hint for a case number — short-circuits court detection, and a leading court name, to this court. An ECLI’s own court segment takes precedence; the hint is searched only for a segment this lookup does not map. A Rechtssatz number (RS0022961) always searches justiz, whatever the hint. Codes: ris_list_reference topic courts, minus normenliste (a norm index, which carries no case numbers).
stateNoBundesland hint — routes a norm to that state’s consolidated law (LrKons) and an LGBl. gazette to that state’s Landesgesetzblatt (LgblAuth, then the legacy Lgbl series for a citation predating the state’s e-Recht switch). Not applied to an ELI, which names its own, or to a state gazette organ carrying its Bundesland ("LGBlNÖ Nr. 72/2016", "LGBlBgld. Nr. 3/1976"), which is searched in the state it names.
citationYesThe legal citation to resolve, e.g. "§ 6 DSG" or "DSG §1", "Art 10 B-VG", "BGBl. I Nr. 165/1999" or "BGBl I 2018/24", "Ro 2026/03/0016" or "VfGH G 13/2025", "ECLI:AT:VFGH:2026:G13.2025", "RS0022961", "VfSlg 19.632/2012", or an RIS ELI link like "https://www.ris.bka.gv.at/eli/bgbl/1974/60/P75/NOR12029618".
in_force_as_ofNoFor a norm, resolve the version in force on this date (YYYY-MM-DD). Defaults to today in Austria. Not applied to an ELI, which names one version.

Output Schema

NameRequiredDescriptionDefault
kindNoWhat the citation parsed as — "unknown" when it did not classify into any route, or is an RIS ELI link in a layout this lookup does not read whose path is no gazette cite followed only by date, language, or format segments, such as a provision’s path cut before its document number ("/eli/bgbl/i/1999/165/A2P4").
errorNoPresent when the call failed. Absent on success.
foundNoTrue when the citation resolved to a single best-matching document.
recordNoThe resolved document, in the same normalized shape the corresponding search tool returns — ris_search_legislation for a norm, ris_search_case_law for a case or collection number, ris_search_gazette for a gazette. Present when found is true.
guidanceNoNext-step guidance naming a concrete tool. Present when found is false.
resolution_noteNoWhich application and filter resolved the citation. Present when found is true.
alternatives_countNoDocuments that also matched beyond the one returned — present only when more than one matched. List them all with the search tool named in resolution_note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / citation / description
      Previous value: -"The legal citation to resolve, e.g. \"§ 6 DSG\" or \"DSG §1\", \"Art 10 B-VG\", \"BGBl. I Nr. 165/1999\" or \"BGBl I 2018/24\", \"Ro 2026/03/0016\" or \"VfGH G 13/2025\", \"ECLI:AT:VFGH:2026:G13.2025\", or \"VfSlg 19.632/2012\"."New value: +"The legal citation to resolve, e.g. \"§ 6 DSG\" or \"DSG §1\", \"Art 10 B-VG\", \"BGBl. I Nr. 165/1999\" or \"BGBl I 2018/24\", \"Ro 2026/03/0016\" or \"VfGH G 13/2025\", \"ECLI:AT:VFGH:2026:G13.2025\", \"RS0022961\", \"VfSlg 19.632/2012\", or an RIS ELI link like \"https://www.ris.bka.gv.at/eli/bgbl/1974/60/P75/NOR12029618\"."
    • changedInput schema / properties / court / description
      Previous value: -"Court hint for a case number — short-circuits court detection, and a leading court name, to this court. An ECLI’s own court segment takes precedence; the hint is searched only for a segment this lookup does not map. Codes: ris_list_reference topic courts, minus normenliste (a norm index, which carries no case numbers)."New value: +"Court hint for a case number — short-circuits court detection, and a leading court name, to this court. An ECLI’s own court segment takes precedence; the hint is searched only for a segment this lookup does not map. A Rechtssatz number (RS0022961) always searches justiz, whatever the hint. Codes: ris_list_reference topic courts, minus normenliste (a norm index, which carries no case numbers)."
    • changedInput schema / properties / in_force_as_of / description
      Previous value: -"For a norm, resolve the version in force on this date (YYYY-MM-DD). Defaults to today in Austria."New value: +"For a norm, resolve the version in force on this date (YYYY-MM-DD). Defaults to today in Austria. Not applied to an ELI, which names one version."
    • changedInput schema / properties / kind / description
      Previous value: -"Force a route, or auto (default) to classify by shape. Set explicitly when the citation shape is ambiguous."New value: +"Force a route, or auto (default) to classify by shape; only auto reads an RIS ELI link. Set explicitly when the citation shape is ambiguous."
    • changedInput schema / properties / state / description
      Previous value: -"Bundesland hint — routes a norm to that state’s consolidated law (LrKons) and an LGBl. gazette to that state’s Landesgesetzblatt (LgblAuth, then the legacy Lgbl series for a citation predating the state’s e-Recht switch)."New value: +"Bundesland hint — routes a norm to that state’s consolidated law (LrKons) and an LGBl. gazette to that state’s Landesgesetzblatt (LgblAuth, then the legacy Lgbl series for a citation predating the state’s e-Recht switch). Not applied to an ELI, which names its own, or to a state gazette organ carrying its Bundesland (\"LGBlNÖ Nr. 72/2016\", \"LGBlBgld. Nr. 3/1976\"), which is searched in the state it names."
    • changedOutput schema / properties / kind / description
      Previous value: -"What the citation parsed as — \"unknown\" when it did not classify into any route."New value: +"What the citation parsed as — \"unknown\" when it did not classify into any route, or is an RIS ELI link in a layout this lookup does not read whose path is no gazette cite followed only by date, language, or format segments, such as a provision’s path cut before its document number (\"/eli/bgbl/i/1999/165/A2P4\")."
  2. Changed2 schema fields changed
    • changedInput schema / properties / citation / description
      Previous value: -"The legal citation to resolve, e.g. \"§ 6 DSG\" or \"DSG §1\", \"Art 10 B-VG\", \"BGBl. I Nr. 165/1999\", \"Ro 2026/03/0016\", or \"VfSlg 19.632/2012\"."New value: +"The legal citation to resolve, e.g. \"§ 6 DSG\" or \"DSG §1\", \"Art 10 B-VG\", \"BGBl. I Nr. 165/1999\" or \"BGBl I 2018/24\", \"Ro 2026/03/0016\" or \"VfGH G 13/2025\", \"ECLI:AT:VFGH:2026:G13.2025\", or \"VfSlg 19.632/2012\"."
    • changedInput schema / properties / court / description
      Previous value: -"Court hint for a case number — short-circuits court detection to this court. Codes: ris_list_reference topic courts, minus normenliste (a norm index, which carries no case numbers)."New value: +"Court hint for a case number — short-circuits court detection, and a leading court name, to this court. An ECLI’s own court segment takes precedence; the hint is searched only for a segment this lookup does not map. Codes: ris_list_reference topic courts, minus normenliste (a norm index, which carries no case numbers)."
  3. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "found",
      +      "kind"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `upstream_error`: A routed RIS search was unreachable, returned a server error, or served an HTML error page. An unparseable or unresolvable citation is NOT this error — it returns found: false. `upstream_timeout`: A routed RIS search did not answer within the request deadline. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "upstream_error",
      +            "upstream_timeout"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "found",
      -  "kind"
      -]
  4. Changed1 schema field changed
    • changedInput schema / properties / state / description
      Previous value: -"Bundesland hint — routes a norm to that state’s consolidated law (LrKons) and an LGBl. gazette to that state’s Landesgesetzblatt (LgblAuth)."New value: +"Bundesland hint — routes a norm to that state’s consolidated law (LrKons) and an LGBl. gazette to that state’s Landesgesetzblatt (LgblAuth, then the legacy Lgbl series for a citation predating the state’s e-Recht switch)."
  5. Changed4 schema fields changed
    • changedInput schema / properties / citation / description
      Previous value: -"The legal citation to resolve, e.g. \"§ 6 DSG\" or \"DSG §1\", \"Art 10 B-VG\", \"BGBl. I Nr. 165/1999\", \"Ra 2019/22/0184\", or \"VfSlg 19.632/2012\"."New value: +"The legal citation to resolve, e.g. \"§ 6 DSG\" or \"DSG §1\", \"Art 10 B-VG\", \"BGBl. I Nr. 165/1999\", \"Ro 2026/03/0016\", or \"VfSlg 19.632/2012\"."
    • changedInput schema / properties / court / description
      Previous value: -"Court hint for a case number — short-circuits court detection to this court. Codes: ris_list_reference topic courts."New value: +"Court hint for a case number — short-circuits court detection to this court. Codes: ris_list_reference topic courts, minus normenliste (a norm index, which carries no case numbers)."
    • changedInput schema / properties / court / enum
      Previous value: -[
      -  "vfgh",
      -  "vwgh",
      -  "justiz",
      -  "bvwg",
      -  "lvwg",
      -  "dsk",
      -  "normenliste",
      -  "dok",
      -  "pvak",
      -  "gbk",
      -  "uvs",
      -  "asylgh",
      -  "ubas",
      -  "umse",
      -  "bks",
      -  "verg",
      -  "upts"
      -]New value: +[
      +  "vfgh",
      +  "vwgh",
      +  "justiz",
      +  "bvwg",
      +  "lvwg",
      +  "dsk",
      +  "dok",
      +  "pvak",
      +  "gbk",
      +  "uvs",
      +  "asylgh",
      +  "ubas",
      +  "umse",
      +  "bks",
      +  "verg",
      +  "upts"
      +]
    • changedInput schema / properties / in_force_as_of / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^\\d{4}-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\\d|3[01])$"
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavior: a miss returns found:false with next-step guidance and never throws, while only an upstream RIS outage is an error. It also explains ambiguity outcomes, alternatives_count, ELI precedence, and detailed ranking and fallback behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening is front-loaded, but the body is an enormous semicolon-heavy paragraph covering many edge cases in dense prose. The information is often relevant, but the structure makes the definition difficult to scan and much longer than needed for a tool description.

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?

For a citation resolver with complex routing and many edge cases, the description is highly complete: it covers route detection, ELI handling, ambiguity, misses, ranking, and output shape. With an output schema and annotations already present, little material information is missing.

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?

Schema description coverage is 100%, so the schema already documents all five parameters, including enums and defaults. The description still adds substantive interpretation rules for citation shapes, forced kind values, and court/state hint interactions, though some of this repeats the schema.

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 opening sentence states a specific verb and resource: resolve a single Austrian legal citation to its canonical RIS document deterministically, with no keyword search. It clearly distinguishes itself from keyword-search siblings and the rest of the description remains consistent with that purpose.

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 explicitly says not to use it for keyword lookup and names the alternatives: ris_search_legislation or ris_search_case_law. It also explains when auto versus forced kind matters and how court, state, and citation shape affect routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.