Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Przestań obserwować spółkę

unwatch_company
DestructiveIdempotent

Wymaga zalogowania (OAuth, scope watchlist:write). Usuwa spółkę z obserwowanych przez 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": "unwatch_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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuinely new context by naming the required OAuth scope and clarifying that the removal applies to the calling reader's own watchlist. It does not mention rate limits or error behavior when the company is not currently watched, leaving some behavioral detail to 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with no filler. The auth prerequisite is front-loaded ahead of the action, which is defensible for a guarded mutation but slightly delays the statement of purpose.

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?

The tool is simple: one documented required parameter, an output schema that covers return values, and annotations that cover destructive/idempotent semantics. With auth scope and per-reader scoping stated, nothing an agent needs to call it correctly is missing.

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?

There is a single parameter and schema coverage is 100%, with the schema already providing the KRS pattern, an example, and a pointer to search_companies. The description adds no meaning beyond that, which is the expected baseline for a fully documented single parameter.

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?

"Usuwa spółkę z obserwowanych przez czytelnika" states a specific verb (removes) and resource (company from the reader's watchlist), and the per-reader scoping distinguishes it from a generic company operation. It stops short of naming its inverse sibling watch_company, so sibling differentiation is only implied by the tool's semantics.

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?

The description gives a prerequisite (logged in, OAuth scope watchlist:write) but no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The use case is strongly implied by the pairing with watch_company, but the agent must infer that this is the undo action.

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