Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Teksty redakcji

search_articles
Read-onlyIdempotent

Opublikowane teksty Dziennika Firm (poradniki o obowiązkach spółek i sprawdzaniu kontrahenta, analizy, wydania): tytuł, dział, data, zajawka, url. Pełny tekst: url z nagłówkiem Accept: text/markdown.

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": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoZapytanie, np. "likwidacja spółki z o.o.", "termin sprawozdania".
dzialNo
limitNo

Output Schema

NameRequiredDescriptionDefault
liczbaYes
tekstyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real value beyond them: it discloses that results are excerpts only and documents the non-obvious Accept: text/markdown mechanism for retrieving full text from the returned url.

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?

Two tight sentences: first the resource plus returned fields, then the non-obvious full-text retrieval instruction. Nothing is padded and the most actionable detail (Accept header) is placed where it is easy to find.

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

Completeness3/5

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

With an output schema present, listing return fields is slightly redundant, and the annotations cover the safety profile, so the definition is serviceable. The remaining gap is parameter meaning — a caller still has to guess how q and dzial interact and what limits apply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only q is documented in the schema; the dzial enum values and limit bounds carry no explanatory text. The description says nothing about how q is matched, how dzial narrows results, or what limit defaults to, so it does not compensate for the coverage gap. The word 'dział' appears only as a returned field, not as an explained 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?

The description names the concrete resource (published Dziennik Firm articles: guides, analyses, editions) and enumerates the returned fields (tytuł, dział, data, zajawka, url), so an agent knows exactly what this returns. It stops short of naming a sibling it is not (e.g. get_article, search_companies), so differentiation is only implicit in the content-type list.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. The only routing hint is implicit: full text is not returned here, it is fetched from the returned url with an Accept: text/markdown header, which suggests using this tool for discovery and the url for reading.

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