Skip to main content
Glama
Sign In

Ärikratt

by ee.arikratt
OverviewDiscussionsAdmin

Browse catalogs

browse_catalog
Read-only

Free paginated catalogs with attribution, source clocks and partial coverage. Follow next_offset; envelope trimming preserves continuation. legal_search: state statutes/regulations, literal FTS5, exact RT ID or title/ID plus §; title, section path and RT link per passage. Tallinn-date validity is checked; new redactions need a snapshot refresh. No vectors, generation, attachments or municipal/individual acts. Medicines: no documents, company joins or clinical inference. IP: no person names, addresses, designers or representatives; organization codes require a legal-entity match. Courts: 2020+ validated metadata only; no names, prose, charges or company/person links. Property: identifiers, addresses, energy labels, parcel links and public state assets; no private owners or quarantine. Ships: open entries and active non-FIE organization observations, not proven current ownership; no mortgages. Inspect dates/status; EHR freshness and ship currentness may be unknown. Use describe_datasets for exclusions. Do not look up natural persons.

Input Schema

NameRequiredDescriptionDefault
kindYesCurrent legal passages, packages, safe IP filings, name-free courts or qualified property
limitNo
queryNoApproved metadata or identifier; empty browses all rows
offsetNo

Output Schema

NameRequiredDescriptionDefault
kindYes
rowsYes
as_ofNoAs of. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.
limitNoLimit. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.
totalYes
noticeNoNotice. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.
offsetYes
statusYes
sourcesYes
coverageYes
truncatedYes
disclaimerNoDisclaimer. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.
next_offsetYes
snapshot_idYes
source_clocksYes
source_detailsNoSource details. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / as_of
      Added value: +{
+  "description": "As of. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+  "type": "string"
+}
    • addedOutput schema / properties / coverage / properties
      Added value: +{
+  "reason": {
+    "description": "Reason. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  },
+  "status": {
+    "description": "Status. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / disclaimer
      Added value: +{
+  "description": "Disclaimer. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+  "type": "string"
+}
    • addedOutput schema / properties / limit
      Added value: +{
+  "description": "Limit. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+  "type": "integer"
+}
    • addedOutput schema / properties / notice
      Added value: +{
+  "description": "Notice. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+  "type": "string"
+}
    • addedOutput schema / properties / source_details
      Added value: +{
+  "description": "Source details. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+  "type": "string"
+}
    • addedOutput schema / properties / sources / items / properties
      Added value: +{
+  "attribution": {
+    "description": "Attribution. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  },
+  "key": {
+    "description": "Key. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  },
+  "licence": {
+    "description": "Licence. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  },
+  "licence_url": {
+    "description": "Licence url. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  },
+  "name": {
+    "description": "Name. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  },
+  "url": {
+    "description": "Url. catalogs.catalog_page and tools.browse_catalog: allowlisted catalog metadata.",
+    "type": "string"
+  }
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Current package, safe IP filing, name-free court metadata or qualified property catalog"New value: +"Current legal passages, packages, safe IP filings, name-free courts or qualified property"
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs",
-  "court_decisions",
-  "buildings",
-  "ehr_energy_labels",
-  "ehr_building_cadastral",
-  "cadastral",
-  "land_register_kris",
-  "land_register_parcels",
-  "state_real_estate_rkvr",
-  "katri_state_property_ownership",
-  "ship_register_safe_projection",
-  "ship_technical_entries",
-  "ship_legal_owners"
-]New value: +[
+  "legal_search",
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions",
+  "buildings",
+  "ehr_energy_labels",
+  "ehr_building_cadastral",
+  "cadastral",
+  "land_register_kris",
+  "land_register_parcels",
+  "state_real_estate_rkvr",
+  "katri_state_property_ownership",
+  "ship_register_safe_projection",
+  "ship_technical_entries",
+  "ship_legal_owners"
+]
    • changedOutput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs",
-  "court_decisions",
-  "buildings",
-  "ehr_energy_labels",
-  "ehr_building_cadastral",
-  "cadastral",
-  "land_register_kris",
-  "land_register_parcels",
-  "state_real_estate_rkvr",
-  "katri_state_property_ownership",
-  "ship_register_safe_projection",
-  "ship_technical_entries",
-  "ship_legal_owners"
-]New value: +[
+  "legal_search",
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions",
+  "buildings",
+  "ehr_energy_labels",
+  "ehr_building_cadastral",
+  "cadastral",
+  "land_register_kris",
+  "land_register_parcels",
+  "state_real_estate_rkvr",
+  "katri_state_property_ownership",
+  "ship_register_safe_projection",
+  "ship_technical_entries",
+  "ship_legal_owners"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs",
-  "court_decisions",
-  "buildings",
-  "ehr_energy_labels",
-  "ehr_building_cadastral",
-  "cadastral"
-]New value: +[
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions",
+  "buildings",
+  "ehr_energy_labels",
+  "ehr_building_cadastral",
+  "cadastral",
+  "land_register_kris",
+  "land_register_parcels",
+  "state_real_estate_rkvr",
+  "katri_state_property_ownership",
+  "ship_register_safe_projection",
+  "ship_technical_entries",
+  "ship_legal_owners"
+]
    • changedOutput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs",
-  "court_decisions",
-  "buildings",
-  "ehr_energy_labels",
-  "ehr_building_cadastral",
-  "cadastral"
-]New value: +[
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions",
+  "buildings",
+  "ehr_energy_labels",
+  "ehr_building_cadastral",
+  "cadastral",
+  "land_register_kris",
+  "land_register_parcels",
+  "state_real_estate_rkvr",
+  "katri_state_property_ownership",
+  "ship_register_safe_projection",
+  "ship_technical_entries",
+  "ship_legal_owners"
+]
  4. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Current package, safe IP filing or name-free court metadata catalog"New value: +"Current package, safe IP filing, name-free court metadata or qualified property catalog"
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs",
-  "court_decisions"
-]New value: +[
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions",
+  "buildings",
+  "ehr_energy_labels",
+  "ehr_building_cadastral",
+  "cadastral"
+]
    • changedOutput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs",
-  "court_decisions"
-]New value: +[
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions",
+  "buildings",
+  "ehr_energy_labels",
+  "ehr_building_cadastral",
+  "cadastral"
+]
  5. Changed4 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Current package or safe IP filing catalog"New value: +"Current package, safe IP filing or name-free court metadata catalog"
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs"
-]New value: +[
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions"
+]
    • changedInput schema / properties / query / description
      Previous value: -"Package/filing text or identifier; empty browses all rows"New value: +"Approved metadata or identifier; empty browses all rows"
    • changedOutput schema / properties / kind / enum
      Previous value: -[
-  "medicines",
-  "trademarks",
-  "designs"
-]New value: +[
+  "medicines",
+  "trademarks",
+  "designs",
+  "court_decisions"
+]
  6. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds valuable operational context beyond annotations: free paginated access, next_offset continuation, envelope trimming, partial coverage, snapshot refresh requirements, and dataset-specific validity/freshness caveats. This is rich behavioral disclosure, though it is disorganized.

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 description is a long, dense, jargon-heavy run-on with semicolon-separated dataset exclusions and no clear hierarchy. It is not front-loaded with the core purpose and forces the reader to parse unrelated constraints before understanding what the tool returns.

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?

An output schema exists, so return values need not be explained. The description attempts to cover each of the 16 kinds and their exclusions, which is helpful for a complex multi-kind tool, but it omits important call behavior such as how limit and offset interact and what an empty query returns for each kind. Adequate but incomplete for the tool's complexity.

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 coverage is 50%: kind and query are documented in the schema, while limit and offset are not. The description adds meaning for query ('literal FTS5, exact RT ID or title/ID plus §') and for pagination ('Follow next_offset'), but does not explain limit's ceiling of 25 or offset's interaction with next_offset beyond a hint. Baseline 3 is appropriate given partial schema coverage and partial compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence 'Free paginated catalogs with attribution, source clocks and partial coverage' is abstract and does not plainly state that this tool browses rows from multiple registry datasets by kind. The per-kind notes partially clarify the resources, but they read as constraint lists rather than a crisp purpose statement, and the tool is not distinguished from siblings like search_legal_vectors or find_companies.

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

Usage Guidelines3/5

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

There is some routing guidance ('Use describe_datasets for exclusions') and a clear prohibition ('Do not look up natural persons'), but no explicit when-to-use-this-vs-alternative guidance for the 16 kinds or for sibling tools such as search_legal_vectors. The agent must infer usage from scattered caveats.

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

All Ärikratt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources