Skip to main content
Glama

regdata_austria_ediktsdatei

Retrieve official Austrian insolvency and court publications from Ediktsdatei. Search bankruptcies, reorganizations, debt settlements, auctions, and firmenbuch announcements by court, state, date, or debtor name.

Instructions

Austria Insolvency & Court Publications Scraper. Scrape Austrian insolvency data from the Ediktsdatei - bankruptcies, reorganizations, debt settlements, court auctions, and Firmenbuch announcements. Official court publications with no API alternative. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
courtNoFilter by court name (e.g. 'Handelsgericht Wien', 'Landesgericht Linz'). Leave empty for all courts. | Nach Gericht filtern. Leer lassen fur alle Gerichte.
stateNoFilter by Austrian federal state. | Nach Bundesland filtern.all
dateToNoOnly return publications up to this date (YYYY-MM-DD). Default: today. | Nur Veroffentlichungen bis zu diesem Datum (JJJJ-MM-TT).
dateFromNoOnly return publications from this date onward (YYYY-MM-DD). Default: 30 days ago. | Nur Veroffentlichungen ab diesem Datum (JJJJ-MM-TT).
maxItemsNoOptional cap on billed dataset items returned.
entryTypeNoFilter by entry type: 'initial' for new proceedings, 'changes' for updates, 'all' for both. | Ersteintrage, Anderungen, oder beides.all
maxResultsNoMaximum number of results to return. Default: 100. Set to 0 for unlimited. | Maximale Anzahl der Ergebnisse.
searchQueryNoName of the debtor or company to search for (minimum 3 characters). Partial match supported. | Name des Schuldners oder Unternehmens (mindestens 3 Zeichen).
proceedingTypeNoType of insolvency proceeding to filter. 'all' returns all types. | Art des Insolvenzverfahrens. 'all' gibt alle Verfahrensarten zuruck.all
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses the tool is a scraper but fails to mention rate limits, authentication, caching, or limitations on date range or result counts.

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

Conciseness5/5

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

The description is concise (3 sentences) and front-loaded with purpose and key details. Every sentence adds value without redundancy.

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?

All 9 parameters are described in the schema, but no output schema exists. The description lacks details on behavior for edge cases (e.g., large date ranges, pagination) and does not fully compensate for missing annotations.

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%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions, except noting that advanced fields are available via regdata_describe.

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 identifies the tool as an Austria-specific insolvency and court publications scraper, listing specific data types and the source (Ediktsdatei). It distinguishes from sibling tools which target other jurisdictions.

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?

The description states there is no API alternative, implying scraping is necessary. It also references 'regdata_describe' for advanced fields, but does not explicitly state when not to use this tool or provide alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nolpak14/getregdata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server