billingo-mcp

Get organization

billingo_get_organization

Read-onlyIdempotent

Retrieve account-level data for the API key's organization—tax code, Billingo subscription, and NAV Online Számla connection—to check subscription or NAV status; not a company profile.

Instructions

Returns account-level data for the organization that owns the API key: its tax code, its Billingo subscription, and whether NAV Online Számla is connected. This is NOT a company profile — it contains no name, id or address. Use it to check the subscription or NAV connection status.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tax_code`	No
`subscription`	No
`has_nav_connection`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.3Oct 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "has_nav_connection": {
+      "type": [
+        "boolean",
+        "number",
+        "null"
+      ]
+    },
+    "subscription": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "additionalProperties": {},
+              "properties": {
+                "expiration_date": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "features": {
+                  "anyOf": [
+                    {
+                      "items": {},
+                      "type": "array"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            {
+              "items": {},
+              "maxItems": 0,
+              "type": "array"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "tax_code": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Sep 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful scope details: the data belongs to the organization owning the API key, includes specific fields, and explicitly excludes company-profile data like name, id, and address. It does not add auth or rate-limit context, but it meaningfully supplements the annotations.

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?

Three short sentences, front-loaded with the return contents, followed by the key exclusion and the use case. Every sentence adds useful information with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not document return values in detail. It explains the scope, included fields, and exclusions well enough to call the tool correctly. The only meaningful gap is not clarifying the relationship with the sibling NAV status tool.

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 is 4. There are no parameter semantics to explain, and the description does not need to compensate for any schema gaps.

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

Purpose4/5

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

The description clearly states the verb and resource: it returns account-level organization data tied to the API key, and specifies tax code, subscription, and NAV connection status. It also explicitly rules out company-profile fields such as name, id, and address. It does not distinguish itself from the sibling billingo_get_online_szamla_status, which also relates to NAV status.

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?

It gives an explicit use case: checking subscription or NAV connection status. However, it does not explain when to use the dedicated sibling billingo_get_online_szamla_status instead, and it provides no further exclusions or prerequisites. The guidance is present but incomplete against the sibling set.

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