Firmafakta

Look up a company

firmafakta_lookup

Read-only

Everything on one company: its facts, figures, workplaces and the lists your plan reaches. Give org_number or ref (from a trademark result), one of them. For many companies use firmafakta_fetch on a segment; for the free public facts, firmafakta_company. How to read the answer is in firmafakta_describe's lookup. Costs credits even when nothing is found; opening the same company again within a day is free.

Input Schema

Name	Required	Description	Default
`ref`	No	a company's ref from a firmafakta_trademarks result, in place of org_number
`org_number`	No	the company's org number, ten digits, with or without hyphen; or give ref

Output Schema

Name	Required	Description	Default
`usage`	Yes
`years`	No
`locked`	No
`parent`	No
`company`	No
`contacts`	No
`reopened`	No
`websites`	No
`not_found`	No
`industries`	No
`procedures`	No
`trademarks`	No
`workplaces`	No
`group_years`	No
`subsidiaries`	No
`annual_reports`	No
`out_of_credits`	No
`secondary_names`	No
`annual_reports_note`	No
`sole_proprietorship`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedNov 2, 2026
- changedInput schema / properties / org_number / description
```
Previous value: -"the company's org number, ten digits, with or without hyphen"New value: +"the company's org number, ten digits, with or without hyphen; or give ref"
```
- addedInput schema / properties / ref
```
Added value: +{
+  "description": "a company's ref from a firmafakta_trademarks result, in place of org_number",
+  "type": "string"
+}
```
- removedInput schema / required
```
Removed value: -[
-  "org_number"
-]
```
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / annual_reports / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / contacts / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / contacts / items / properties / sources / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / group_years / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / industries / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / locked / items / additionalProperties
```
Removed value: -false
```
- addedOutput schema / properties / out_of_credits
```
Added value: +{
+  "type": "boolean"
+}
```
- removedOutput schema / properties / parent / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / procedures / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / secondary_names / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / subsidiaries / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / trademarks / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / trademarks / items / properties / goods / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / usage / additionalProperties
```
Removed value: -false
```
- addedOutput schema / properties / usage / properties / offer
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / usage / properties / throttled / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / websites / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / years / items / additionalProperties
```
Removed value: -false
```

Changed4 schema fields changedOct 24, 2026

addedOutput schema / properties / contacts

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "type": "string"
+      },
+      "sources": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "page_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name"
+          ],
+          "type": "object"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value",
+      "sources"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / parent

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "fiscal_year_end": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "orgnr": {
+      "type": "string"
+    },
+    "ref": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "orgnr",
+    "name",
+    "fiscal_year_end"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

addedOutput schema / properties / subsidiaries

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "orgnr": {
+        "type": "string"
+      },
+      "ref": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "orgnr",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / websites

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "booking": {
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "careers_page": {
+        "type": "boolean"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "languages": {
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "mail_provider": {
+        "type": "string"
+      },
+      "platforms": {
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "read_at": {
+        "type": [
+          "null",
+          "string"
+        ]
+      },
+      "recruiting": {
+        "type": "boolean"
+      },
+      "recruitment_systems": {
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "shop": {
+        "type": "boolean"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "url",
+      "shop",
+      "platforms",
+      "recruiting",
+      "recruitment_systems",
+      "careers_page",
+      "booking",
+      "languages"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent/destructive flags; the description adds the things annotations cannot say — that credits are charged even on a miss, and that re-opening the same company within a day is free. That cost and caching behavior is exactly the non-obvious context an agent needs before calling a metered lookup.

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?

Dense and front-loaded: what it returns, then inputs, then alternatives, then cost. A couple of phrases are cryptic on first read ("the lists your plan reaches", "firmafakta_describe's lookup"), but no sentence is filler.

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 format need not be explained, and the description covers the remaining gaps: which sibling to use, acceptable inputs, credit cost, and caching. Nothing an agent needs to call this 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 schema already documents both fields, but the description adds meaning the schema does not: only one of org_number or ref is needed, and ref comes specifically from a trademark result. The unresolved conflict is that both schema fields are optional, so "one of them" is the only signal that one is effectively required.

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?

"Everything on one company: its facts, figures, workplaces and the lists your plan reaches" states a specific verb-and-resource plus the scope of what is returned. It explicitly separates itself from firmafakta_fetch (many companies on a segment) and firmafakta_company (free public facts), so an agent can pick 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?

Names two alternatives with the exact condition that selects each: firmafakta_fetch for many companies via a segment, firmafakta_company for free public facts. It also points to firmafakta_describe's lookup for interpreting results, leaving nothing to inference.

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

All Firmafakta 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.