pl-firmy: Polish company check

Monitor a contractor (daily)

add_watch

Idempotent

Once a day, check one Polish contractor (one NIP) in public registries. The check reads VAT status and white-list bank accounts from the Ministry of Finance, and reads KRS for liquidation, bankruptcy or restructuring. It stores the NIP, any bank accounts you choose to watch, an optional label, and a snapshot of that check. Change alerts go only to the e-mail of the signed-in account owner (the OAuth-linked KSeF Płatności account, or the owner of the almmity API key). It never e-mails the contractor and it never contacts anyone else. It does not accept a webhook address or another e-mail address. If this account has no e-mail on file, the watch is still stored and alerts are visible with list_watches and in the panel. Adding the same NIP again updates that watch. Stop monitoring with remove_watch. Requires sign-in (OAuth) or an almmity API key. Does not accept a KSeF token or a password.

Input Schema

Name	Required	Description
`nip`	Yes	Polish NIP of the one contractor to monitor.
`label`	No	Optional label stored with this NIP.
`accounts`	No	Bank accounts you pay this contractor to. Optional.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 22, 2026

changedInput schema / properties / accounts / description

Previous value: -"Bank accounts you pay this contractor to"New value: +"Bank accounts you pay this contractor to. Optional."

removedInput schema / properties / email

Removed value: -{
-  "format": "email",
-  "maxLength": 200,
-  "type": "string"
-}

addedInput schema / properties / label / description

Added value: +"Optional label stored with this NIP."

addedInput schema / properties / nip / description

Added value: +"Polish NIP of the one contractor to monitor."

removedInput schema / properties / webhook_url

Removed value: -{
-  "format": "uri",
-  "maxLength": 500,
-  "type": "string"
-}

Changed5 schema fields changedOct 22, 2026
- addedInput schema / properties / accounts / maxItems
```
Added value: +20
```
- addedInput schema / properties / email / maxLength
```
Added value: +200
```
- addedInput schema / properties / label / maxLength
```
Added value: +120
```
- addedInput schema / properties / webhook_url / maxLength
```
Added value: +500
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
```
First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say write/idempotent/non-destructive; the description adds the daily cadence, the external data sources, that alerts go only to the signed-in owner's e-mail and never to the contractor, that no webhook or alternate address is accepted, and the no-e-mail-on-file fallback. This is precisely the beyond-schema context the description should carry.

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?

Front-loaded with the core action and scope, then layered with behavior. It is dense rather than padded, though the run of negative constraints (no webhook, no other e-mail, no KSeF token, no password) could be tightened slightly.

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?

A mutating, scheduled, externally-sourced tool with an output schema present — the description covers scheduling, data provenance, notification routing, idempotency, removal path, and auth. Nothing material is left for the agent to guess.

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 baseline is 3, but the description adds meaning: 'any bank accounts you choose to watch' clarifies that accounts are monitored for change alerts rather than merely stored, and the label is described as stored metadata. The NIP is an unmodified repeat of the schema.

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?

Specific verb and resource with scope: 'check one Polish contractor (one NIP) in public registries', plus exactly which registries and data are read. It distinguishes itself from list_watches and remove_watch by name and function.

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?

Explicitly states the upsert rule ('Adding the same NIP again updates that watch') and names remove_watch as the way to stop. Auth requirements are given with exclusions ('does not accept a KSeF token or a password'), which is exactly the when/when-not guidance an agent needs.

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

All pl-firmy: Polish company check 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.