Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Obserwuj spółkę

watch_company
Idempotent

Wymaga zalogowania (OAuth, scope watchlist:write). Dodaje spółkę z bazy Dziennika Firm do obserwowanych przez czytelnika (najwyżej 50). Po zamknięciu każdego wydania czytelnik dostaje e-mail z nowymi wpisami w KRS obserwowanych spółek. Używaj tylko na wyraźną prośbę czytelnika.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "krs": "<krs>"
    },
    "name": "watch_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
krsYesNumer KRS spółki (search_companies), np. "0000915798".

Output Schema

NameRequiredDescriptionDefault
liczbaYes
spolkiYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false), the description discloses the required OAuth scope, the 50-company cap, and the consequential side effect of a post-edition e-mail digest of new KRS entries. That is exactly the kind of behavioral context annotations cannot convey.

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?

Four short sentences, front-loaded with the authentication requirement, then effect, then side effect, then usage policy. Nothing is repeated from the schema and 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 values need no explanation. Auth requirements, the watchlist cap, the e-mail side effect, and the explicit-request policy together cover everything an agent needs before mutating a watchlist.

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 100% for the single 'krs' parameter, and the schema itself documents the KRS number format and points at search_companies. The description reinforces that the company comes from the Dziennik Firm database but adds no format or validation detail beyond the schema, so the baseline 3 applies.

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 description names a specific verb and resource: it adds a company from the Dziennik Firm database to the reader's watchlist. The scope (max 50) and source database make it unmistakable and clearly distinct from unwatch_company or list_my_watchlist.

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

Usage Guidelines4/5

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

It states an explicit gating condition: 'Używaj tylko na wyraźną prośbę czytelnika' (use only on an explicit reader request). Prerequisites (login, OAuth scope watchlist:write) are also spelled out. It does not name unwatch_company as the inverse alternative, so it stops short of full when/when-not routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources