Ärikratt

Economic context

economy_context

Read-only

National context: real gross domestic product (GDP) annual growth, month-end registered unemployed counts and annualised volume-weighted contractual interest rates on new and amended euro loans to Estonian resident non-financial corporations. Growth uses chain-linked, unadjusted, revisable volume accounts, not flash estimates; unemployment is a count, not a rate; interest is not outstanding-loan interest. The official corporate aggregate includes sole proprietors with 10+ employees. Each series includes observation periods, units, basis, cadence and source licences, with up to eight observations. Old snapshots return empty rows; truncated results retain totals. Use region_stats for counties or sector_stats for company benchmarks. Do not look up natural persons or household credit data.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`rows`	Yes
`as_of`	Yes
`sources`	Yes
`truncated`	No
`disclaimer`	Yes
`rows_total`	Yes
`snapshot_id`	Yes
`source_details`	Yes	Full attribution and acquisition evidence: source_metadata(key).
`omitted_sections`	No	Sections removed to fit the response budget, including default sections. Request one named section to retrieve it. Present only when truncated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 18, 2026

addedOutput schema / properties / omitted_sections

Added value: +{
+  "description": "Sections removed to fit the response budget, including default sections. Request one named section to retrieve it. Present only when truncated.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / source_details

Added value: +{
+  "description": "Full attribution and acquisition evidence: source_metadata(key).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / sources / items / properties / as_of
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / sources / items / properties / key
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / required

Previous value: -[
-  "snapshot_id",
-  "as_of",
-  "sources",
-  "disclaimer",
-  "rows",
-  "rows_total"
-]New value: +[
+  "snapshot_id",
+  "as_of",
+  "sources",
+  "source_details",
+  "disclaimer",
+  "rows",
+  "rows_total"
+]

AddedOct 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, non-destructive, closed-world), yet the description adds substantial operational context: chain-linked revisable accounts rather than flash estimates, count-not-rate unemployment, the sole-proprietor inclusion rule, up to eight observations, empty rows for old snapshots, and truncated results retaining totals. These are exactly the caveats an agent needs to interpret results without mis-signalling data.

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?

Nearly every clause carries semantic weight (series definitions, caveats, metadata, edge cases, routing), and the routing/exclusion guidance is appropriately placed at the end. The second sentence is a dense run-on that could be split for scannability, which keeps it just short of a 5.

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?

An output schema exists, so return structure need not be described; the description instead supplies the semantics, data-quality caveats, metadata fields per series, and sibling routing. For a parameterless context tool this is complete.

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 tool takes zero parameters, so the baseline of 4 applies; there is no parameter surface for the description to clarify or for the schema to document. No deduction is warranted here beyond the baseline.

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 names the exact resource and enumerates the three series (GDP annual growth, registered unemployed counts, volume-weighted contractual interest rates on new/amended euro loans to Estonian non-financial corporations). It explicitly positions itself against siblings (region_stats for counties, sector_stats for company benchmarks), so an agent can distinguish it without opening a schema.

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 to the correct alternative for two concrete cases and states an exclusion ('Do not look up natural persons or household credit data'), which is the when-not guidance most definitions omit. Nothing about selection is left to inference.

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

All Ärikratt tools Inspect

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

Need Help?