Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

O serwisie

get_site_info
Read-onlyIdempotent

Fakty o Dzienniku Firm: wydawca (JG INVEST P.S.A.), redakcja, źródła danych i metodyka, zasady (bez danych osób fizycznych), liczba spółek w bazie, obserwowane spółki.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlYes
odczytNo

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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it discloses the data policy ('bez danych osób fizycznych') and enumerates the categories of facts returned, which goes beyond 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?

A single front-loaded sentence states the subject and then lists the included facts with no filler. The list is dense but compact, and nothing needs to be removed.

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 return-value explanation is unnecessary, and with no parameters the only remaining need is telling the agent what the tool surfaces, which the description does. A minor gap is not clarifying whether the company count and watched-company list are static site facts or live data.

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 zero parameters, so the baseline is 4; nothing in the description needs to explain argument meaning because there are none.

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 resource (site facts about 'Dziennik Firm') and enumerates its concrete contents: publisher, editorial team, data sources, methodology, data policy, company count, and watched companies. It does not explicitly contrast with siblings, but the enumerated contents are distinctive enough that an agent can tell it apart from get_article or get_company without opening the schema.

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?

Usage is only implied: an agent can infer it should call this when asked about the publisher, methodology, or data policy. There is no explicit when-to-use statement, no exclusions, and no mention of alternatives such as search_articles for content questions.

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