Skip to main content
Glama

Search Austrian Legislation

ris_search_legislation
Read-onlyIdempotent

Search Austrian consolidated law and English translations: federal law (scope: federal, the default), one Bundesland (scope: burgenland … wien), municipal law (municipality plus a state scope — selected norms in 6 Bundesländer), or English translations of selected federal laws (language: english, federal only, ~138 documents). One document is one § / Artikel / Anlage; fetch a whole law by filtering law_id. Searches apply the version in force today in Austria by default — set in_force_as_of for another date, include_all_versions: true for full version history, or an entered_force / left_force window for new-law and repeal tracking; the three version filters are mutually exclusive, and the applied date is echoed back in the result. query is full text (boolean UND/ODER/NICHT or AND/OR/NOT, trailing-only * wildcard); title matches title, short title, and abbreviation ("DSG"). For a specific citation like "§ 6 DSG", ris_lookup_citation resolves it deterministically instead. Consolidated text is informational, not legally binding — the authentic gazette artifact lives in ris_search_gazette.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ris_search_legislation"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based result page. Default 1.
indexNoSystematik classification filter (e.g. "10/10 Datenschutz"). Federal/state consolidated law only. Omit to leave unfiltered; a blank value is rejected.
queryNoFull-text search (Suchworte). Boolean operators UND/ODER/NICHT or AND/OR/NOT, parentheses, quoted phrases; wildcard * is trailing-only ("Datenschutz*", never "*schutz"). Syntax: ris_list_reference topic search_syntax. Omit to leave unfiltered; a blank value is rejected.
scopeNoJurisdiction: federal (default) searches consolidated federal law; a Bundesland searches that state’s consolidated law (or, with municipality set, its municipal law).federal
titleNoTitle search (Titel) — matches title, short title, and official abbreviation ("ABGB", "DSG"). Phrase field: * allowed leading or trailing with ≥2 characters beside it. Omit to leave unfiltered; a blank value is rejected.
law_idNoLaw-level grouping key (Gesetzesnummer, e.g. 10001597 = DSG) — exact match; returns every section of that law. Federal/state consolidated law only. Omit to leave unfiltered; a blank value is rejected.
sort_byNoSort column: section (§/Artikel/Anlage label) or in_force_date. Default: upstream order. Federal/state consolidated law only.
languageNogerman (default) searches the authoritative German corpus; english searches the ~138 unofficial English translations of selected federal laws (requires scope: federal; combines only with query and title).german
page_sizeNoDocuments per page, 1–100 (default 20). Served as a page of 10 (1–10) or 20 (11–100), with a notice when that differs. For more results, keep the size and raise page.
section_toNoEnd of the section range. Equal to section_from for a single section. Omit to leave unfiltered; a blank value is rejected.
municipalityNoMunicipality name for municipal law (e.g. "Graz" — RIS’s spelling, not "Stadt Graz"). Requires a state scope; combines only with query, title, and in_force_as_of. Coverage is selected norms in 6 Bundesländer (no Burgenland/Tirol/Vorarlberg). Omit to search consolidated law; a blank value is rejected.
section_fromNoStart of a § / Artikel / Anlage number range, digits with optional letter ("6", "1a"). Federal/state consolidated law only. Omit to leave unfiltered; a blank value is rejected.
section_typeNoWhich section kind the range addresses. Defaults to Paragraph when a section range is set. Values: ris_list_reference topic section_types.
changed_sinceNoCoarse recency filter — documents changed in RIS within the interval. For exact windows and deletions use ris_track_changes.
left_force_toNoProvisions that left force on/before this date (YYYY-MM-DD).
in_force_as_ofNoReturn only the version in force on this date (YYYY-MM-DD). DEFAULTS TO TODAY in Austria — omitting it never searches all historical versions; opt into that with include_all_versions.
sort_directionNoSort direction; applies with sort_by.
left_force_fromNoProvisions that left force on/after this date (YYYY-MM-DD) — repeal tracking. Same exclusivity as entered_force_from. Without left_force_to, RIS also returns versions with no recorded end date, which carry no in_force_until; set both bounds to exclude them.
entered_force_toNoProvisions that entered force on/before this date (YYYY-MM-DD). Without entered_force_from, RIS also returns versions with no recorded entry-into-force date, which carry no in_force_from; set both bounds to exclude them.
entered_force_fromNoProvisions that entered force on/after this date (YYYY-MM-DD) — new-law tracking. Federal/state consolidated law only; mutually exclusive with in_force_as_of and include_all_versions.
include_all_versionsNotrue searches every historical version (no in-force date filter) — version-history research. Overrides in_force_as_of; mutually exclusive with the force-window filters.

Output Schema

NameRequiredDescriptionDefault
pageNo1-based page number RIS served.
errorNoPresent when the call failed. Absent on success.
noticeNoThe served page size when it differs from page_size; then, under a force window open on one side (entered_force_to without entered_force_from, left_force_from without left_force_to), how many rows on this page have no date on that side and the bound that excludes them; then zero-hit guidance — the likely cause and the concrete next call. A reversed force window (entered_force_from later than entered_force_to, or left_force_from later than left_force_to) is answered without a RIS request: 0 documents, and the swapped bounds to retry with in place of the guidance.
resultsNoMatching documents for the requested page. Totals and paging in enrichment.
pageSizeNoPage size RIS applied.
truncatedNoPresent and true when more pages exist beyond this one — raise page to continue.
totalCountNoTotal matching documents across all pages.
appliedInForceAsOfNoThe in-force date the server actually applied (defaulted to today in Austria when omitted). Absent when include_all_versions, a force-window, or language: english searched without a date filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / properties / results / items / properties / eli / description
      Previous value: -"European Legislation Identifier, where assigned (federal coverage is best)."New value: +"European Legislation Identifier of this provision, where RIS assigns one (consolidated federal and state law). Pass it to ris_get_document as document_url to read the provision."
    • addedOutput schema / properties / results / items / properties / latest_change_gazette
      Added value: +{
      +  "description": "Gazette of the latest change to this version of this provision (Novelle) — not of the whole law — organ and number in RIS’s spelling, e.g. \"BGBl. I Nr. 70/2024\". latest_change_relation says what it did. Pass it to ris_lookup_citation for the gazette entry that made the change: a BGBl., RGBl., or StGBl. cite resolves as written, as does a state gazette whose organ carries its Bundesland (\"LGBlNÖ Nr. 72/2016\"); a plain LGBl. cite needs state set to the record’s Bundesland; other organs do not resolve there. Absent when RIS records no change.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / latest_change_relation
      Added value: +{
      +  "description": "What latest_change_gazette did to this version, verbatim from RIS: \"zuletzt geändert durch\" (last amended by), \"aufgehoben durch\" (repealed by), or \"wiederverlautbart durch\" (republished by). Absent when RIS records none.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / original_gazette
      Added value: +{
      +  "description": "Gazette that first promulgated the law (Stammnorm), organ and number in RIS’s spelling, e.g. \"BGBl. I Nr. 165/1999\", \"LGBl Nr 27/2022\". Pass it to ris_lookup_citation for the gazette entry: a BGBl., RGBl., or StGBl. cite resolves as written, as does a state gazette whose organ carries its Bundesland (\"LGBlNÖ Nr. 72/2016\", \"LGBlBgld. Nr. 3/1976\"); a plain LGBl. cite needs state set to the record’s Bundesland; other organs RIS records (dRGBl., GZ, VBl. Tirol, ABl., GVBlTirVbg., Niederösterreich’s systematic LGBl. 6075-1) do not resolve there. Consolidated federal and state law only.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / properties / promulgation / description
      Previous value: -"Promulgation reference (Kundmachungsorgan), e.g. \"BGBl. I Nr. 165/1999\"."New value: +"Promulgation reference (Kundmachungsorgan), e.g. \"BGBl. I Nr. 165/1999 zuletzt geändert durch BGBl. I Nr. 70/2024\" — the join of original_gazette, latest_change_relation, and latest_change_gazette on consolidated law."
  2. Changed3 schema fields changed
    • changedInput schema / properties / entered_force_to / description
      Previous value: -"Provisions that entered force on/before this date (YYYY-MM-DD)."New value: +"Provisions that entered force on/before this date (YYYY-MM-DD). Without entered_force_from, RIS also returns versions with no recorded entry-into-force date, which carry no in_force_from; set both bounds to exclude them."
    • changedInput schema / properties / left_force_from / description
      Previous value: -"Provisions that left force on/after this date (YYYY-MM-DD) — repeal tracking. Same exclusivity as entered_force_from."New value: +"Provisions that left force on/after this date (YYYY-MM-DD) — repeal tracking. Same exclusivity as entered_force_from. Without left_force_to, RIS also returns versions with no recorded end date, which carry no in_force_until; set both bounds to exclude them."
    • changedOutput schema / properties / notice / description
      Previous value: -"The served page size when it differs from page_size, then zero-hit guidance — the likely cause and the concrete next call."New value: +"The served page size when it differs from page_size; then, under a force window open on one side (entered_force_to without entered_force_from, left_force_from without left_force_to), how many rows on this page have no date on that side and the bound that excludes them; then zero-hit guidance — the likely cause and the concrete next call. A reversed force window (entered_force_from later than entered_force_to, or left_force_from later than left_force_to) is answered without a RIS request: 0 documents, and the swapped bounds to retry with in place of the guidance."
  3. Changed7 schema fields changed
    • changedInput schema / properties / page_size / description
      Previous value: -"Documents per page: 10 or 20 (default 20). For more results, keep the size and raise page."New value: +"Documents per page, 1–100 (default 20). Served as a page of 10 (1–10) or 20 (11–100), with a notice when that differs. For more results, keep the size and raise page."
    • removedInput schema / properties / page_size / enum
      Removed value: -[
      -  10,
      -  20
      -]
    • addedInput schema / properties / page_size / maximum
      Added value: +100
    • addedInput schema / properties / page_size / minimum
      Added value: +1
    • changedInput schema / properties / page_size / type
      Previous value: -"number"New value: +"integer"
    • changedOutput schema / properties / notice / description
      Previous value: -"Zero-hit guidance — names the likely cause and the concrete next call."New value: +"The served page size when it differs from page_size, then zero-hit guidance — the likely cause and the concrete next call."
    • changedOutput schema / properties / results / items / properties / in_force_until / description
      Previous value: -"Date this version left force (Ausserkrafttretensdatum). Absent while in force."New value: +"Last day this version is in force (Ausserkrafttretensdatum). Absent when RIS records no end date, which does not mean the version is in force now: it can start in the future. RIS writes 9000-01-01 for a date still awaiting an event. The version is in force on date D when in_force_from ≤ D and in_force_until is absent or ≥ D."
  4. Changed1 schema field changed
    • addedOutput schema / properties / results / items / properties / keywords
      Added value: +{
      +  "description": "Keywords (Schlagworte), where present (consolidated federal and state law).",
      +  "type": "string"
      +}
  5. Changed18 schema fields changed
    • changedInput schema / properties / index / description
      Previous value: -"Systematik classification filter (e.g. \"10/10 Datenschutz\"). Federal/state consolidated law only."New value: +"Systematik classification filter (e.g. \"10/10 Datenschutz\"). Federal/state consolidated law only. Omit to leave unfiltered; a blank value is rejected."
    • addedInput schema / properties / index / pattern
      Added value: +"\\S"
    • changedInput schema / properties / law_id / description
      Previous value: -"Law-level grouping key (Gesetzesnummer, e.g. 10001597 = DSG) — exact match; returns every section of that law. Federal/state consolidated law only."New value: +"Law-level grouping key (Gesetzesnummer, e.g. 10001597 = DSG) — exact match; returns every section of that law. Federal/state consolidated law only. Omit to leave unfiltered; a blank value is rejected."
    • addedInput schema / properties / law_id / pattern
      Added value: +"\\S"
    • changedInput schema / properties / municipality / description
      Previous value: -"Municipality name for municipal law (e.g. \"Graz\" — RIS’s spelling, not \"Stadt Graz\"). Requires a state scope; combines only with query, title, and in_force_as_of. Coverage is selected norms in 6 Bundesländer (no Burgenland/Tirol/Vorarlberg)."New value: +"Municipality name for municipal law (e.g. \"Graz\" — RIS’s spelling, not \"Stadt Graz\"). Requires a state scope; combines only with query, title, and in_force_as_of. Coverage is selected norms in 6 Bundesländer (no Burgenland/Tirol/Vorarlberg). Omit to search consolidated law; a blank value is rejected."
    • addedInput schema / properties / municipality / pattern
      Added value: +"\\S"
    • removedInput schema / properties / page_size / anyOf
      Removed value: -[
      -  {
      -    "const": 10,
      -    "type": "number"
      -  },
      -  {
      -    "const": 20,
      -    "type": "number"
      -  },
      -  {
      -    "const": 50,
      -    "type": "number"
      -  },
      -  {
      -    "const": 100,
      -    "type": "number"
      -  }
      -]
    • changedInput schema / properties / page_size / description
      Previous value: -"Documents per page — RIS accepts 10, 20, 50, or 100. Default 20."New value: +"Documents per page: 10 or 20 (default 20). For more results, keep the size and raise page."
    • addedInput schema / properties / page_size / enum
      Added value: +[
      +  10,
      +  20
      +]
    • addedInput schema / properties / page_size / type
      Added value: +"number"
    • changedInput schema / properties / query / description
      Previous value: -"Full-text search (Suchworte). Boolean operators UND/ODER/NICHT or AND/OR/NOT, parentheses, quoted phrases; wildcard * is trailing-only (\"Datenschutz*\", never \"*schutz\"). Syntax: ris_list_reference topic search_syntax."New value: +"Full-text search (Suchworte). Boolean operators UND/ODER/NICHT or AND/OR/NOT, parentheses, quoted phrases; wildcard * is trailing-only (\"Datenschutz*\", never \"*schutz\"). Syntax: ris_list_reference topic search_syntax. Omit to leave unfiltered; a blank value is rejected."
    • addedInput schema / properties / query / pattern
      Added value: +"\\S"
    • changedInput schema / properties / section_from / description
      Previous value: -"Start of a § / Artikel / Anlage number range, digits with optional letter (\"6\", \"1a\"). Federal/state consolidated law only."New value: +"Start of a § / Artikel / Anlage number range, digits with optional letter (\"6\", \"1a\"). Federal/state consolidated law only. Omit to leave unfiltered; a blank value is rejected."
    • addedInput schema / properties / section_from / pattern
      Added value: +"\\S"
    • changedInput schema / properties / section_to / description
      Previous value: -"End of the section range. Equal to section_from for a single section."New value: +"End of the section range. Equal to section_from for a single section. Omit to leave unfiltered; a blank value is rejected."
    • addedInput schema / properties / section_to / pattern
      Added value: +"\\S"
    • changedInput schema / properties / title / description
      Previous value: -"Title search (Titel) — matches title, short title, and official abbreviation (\"ABGB\", \"DSG\"). Phrase field: * allowed leading or trailing with ≥2 characters beside it."New value: +"Title search (Titel) — matches title, short title, and official abbreviation (\"ABGB\", \"DSG\"). Phrase field: * allowed leading or trailing with ≥2 characters beside it. Omit to leave unfiltered; a blank value is rejected."
    • addedInput schema / properties / title / pattern
      Added value: +"\\S"
  6. 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": [
      +      "results",
      +      "totalCount",
      +      "page",
      +      "pageSize"
      +    ]
      +  },
      +  {
      +    "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: `scope_filter_mismatch`: A filter was combined with a scope, municipality, or language that does not support it, or mutually exclusive version filters were combined — rejected locally before any upstream call; the message names the offending pair. `invalid_query`: A page past the last page of results, or RIS rejecting a parameter value in-band — the Client error message is passed through verbatim, in German. It names the invalid element and its valid values, except for a page past the end, which names no parameter at all. Unsupported filter combinations are caught earlier as scope_filter_mismatch. `upstream_error`: RIS is unreachable, returned a server error, or served an HTML error page. `upstream_timeout`: RIS did not answer the search within the request deadline. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "scope_filter_mismatch",
      +            "invalid_query",
      +            "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: -[
      -  "results",
      -  "totalCount",
      -  "page",
      -  "pageSize"
      -]
  7. Changed5 schema fields changed
    • changedInput schema / properties / entered_force_from / 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])$"
    • changedInput schema / properties / entered_force_to / 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])$"
    • 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])$"
    • changedInput schema / properties / left_force_from / 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])$"
    • changedInput schema / properties / left_force_to / 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])$"
  8. Changed1 schema field changed
    • addedOutput schema / properties / results / items / properties / translation
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Provenance of an unofficial English translation. Present only on Erv records (language: english), which carry no in_force_from, promulgation, or eli of their own — this is the only statement of which German version the text corresponds to, and how old it is.",
      +  "properties": {
      +    "author": {
      +      "description": "Body that produced the translation, e.g. \"Federal Chancellery\".",
      +      "type": "string"
      +    },
      +    "source": {
      +      "description": "Which German version this translation renders, as RIS states it — the originating gazette, the last amendment applied, and the date of the version, one per line.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  9. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, and idempotent, so the safety profile is covered. The description adds non-obvious behavior beyond that: searches default to the version in force today in Austria, the applied date is echoed back, the three version filters are mutually exclusive, and the consolidated text is not legally binding. Some of this overlaps the schema descriptions, keeping it from a 5.

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 and dense, with no filler sentences; every clause carries scope, version, or routing information. It is long and semicolon-heavy, which makes it harder to scan, but the density is justified by the 21-parameter surface and no sentence is wasted.

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 complex 21-parameter tool with an output schema and annotations, the description covers the searchable corpora, document granularity, version semantics and exclusivity, query/title syntax, municipal coverage caveats, and sibling alternatives. Nothing an agent needs in order to call it correctly 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 coverage is 100%, so the baseline is 3. The description still adds conceptual meaning: it explains that one document is one section, that filtering law_id fetches an entire law, that query supports UND/ODER/NICHT or AND/OR/NOT with trailing-only wildcards, and that title matches abbreviations like 'DSG' — useful framing beyond the field-level schema text.

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 verb and resource ('Search Austrian consolidated law and English translations') and immediately enumerates the four searchable corpora (federal, one Bundesland, municipal, English translations). It also defines document granularity ('One document is one § / Artikel / Anlage') and states how to retrieve a whole law via law_id, so an agent can tell exactly what this tool returns and how it differs from sibling searches.

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?

It routes the agent explicitly: use ris_lookup_citation for deterministic citation resolution like '§ 6 DSG', and ris_search_gazette for the authentic gazette artifact, while this tool is informational consolidated text. It also names ris_track_changes for exact windows and deletions, and ris_list_reference for syntax, giving clear alternatives with conditions.

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.