Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Tekst redakcji

get_article
Read-onlyIdempotent

Jeden opublikowany tekst po slugu (z search_articles): tytuł, dział, daty, zajawka, spis treści. Pełny tekst: url z Accept: text/markdown.

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": {
      "slug": "<slug>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
urlYes
odczytNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely useful context beyond that: only published texts are returned, the response contains metadata rather than body text, and full content is fetched from a url using 'Accept: text/markdown'. It still says nothing about what happens for a draft, unpublished, or nonexistent slug, which matters precisely because the tool is described as returning 'published' texts.

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?

It is front-loaded and very short, with no filler sentences. The telegraphic phrasing ('Pełny tekst: url z Accept: text/markdown') takes a moment to parse but carries the one operationally important instruction without overhead.

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?

An output schema exists, so the description need not explain the returned fields it lists; the remaining gap is modest for a one-parameter, read-only tool. The only real shortfall is the missing behavior for missing or unpublished slugs, which is relevant given how common that case would be.

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 description coverage is 0%, so the description has to compensate for the single parameter. It does add the most valuable semantic, namely the slug's provenance from search_articles, but it gives no further detail on the slug itself (the schema pattern already constrains its shape). That is a partial compensation, so a 3 is the fair baseline-plus.

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 resource ('Jeden opublikowany tekst') plus its key ('po slugu') and enumerates what comes back (title, section, dates, lead, table of contents). The parenthetical '(z search_articles)' distinguishes it from the sibling search tool, so an agent can tell the two apart without opening either schema.

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?

Pointing out that the slug comes from search_articles establishes the clear usage context: search first, then fetch the single article by slug. There is no explicit when-not guidance or handling of slugs that are unpublished or unknown.

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