Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Moje obserwowane spółki

list_my_watchlist
Read-onlyIdempotent

Wymaga zalogowania (OAuth, scope watchlist:read). Lista spółek obserwowanych przez zalogowanego czytelnika: nazwa, KRS, status w KRS, ostatni wpis, od kiedy obserwuje, url karty; czy powiadomienia e-mail są włączone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
liczbaYes
spolkiYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond them: the OAuth scope required and the fact that results are scoped to the authenticated reader with e-mail notification status included.

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?

A single compact sentence with the authentication requirement front-loaded, followed by the result contents. No filler and nothing repeated.

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?

For a zero-parameter read tool with an output schema and full annotation coverage, the description supplies the one thing structured fields cannot: the auth/scope requirement and per-user scoping. Enumerating return fields slightly duplicates the output schema but does no harm.

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 no parameters, so there is nothing to disambiguate and the baseline applies. The description correctly focuses on scope (current authenticated reader) rather than inventing parameter detail.

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 uses a specific verb and resource ('Lista spółek obserwowanych przez zalogowanego czytelnika') and enumerates the returned fields (nazwa, KRS, status, ostatni wpis, url karty). It implicitly separates itself from watch_company/unwatch_company by describing a read-only listing, though it never names those siblings explicitly.

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 states the prerequisite (must be logged in, OAuth scope watchlist:read) but gives no explicit when-to-use or when-not-to-use guidance relative to alternatives such as get_company or the watch/unwatch tools. The read-only listing intent is inferable but not spelled out.

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