Skip to main content
Glama
sophymarine

openregistry

by sophymarine
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

List change-notification batches or fetch one (CZ only)

list_change_batches
Read-onlyIdempotent

Retrieve incremental delta batches listing company IDs that changed in a source register (CZ only). Use list mode to browse recent batches; supply a batch_id and source to see individual change records (INS, UPD, DEL) with pagination.

Instructions

Access the change-batch feed — incremental delta batches listing every company ID that changed in a given source register during a given reporting period. Currently only available for CZ; other jurisdictions return 501.

Two modes:

  1. List mode (omit batch_id): returns the N latest batches, optionally filtered by source. Page forward via offset/limit until the returned array is empty — the upstream has no total-count field.

  2. Detail mode (supply batch_id + source): returns change records in that batch with typZmeny ∈ {INS, UPD, DEL} and the changed company ID. Response also carries total_changes (full batch size) and pagination: { limit, offset, has_more }. Client-side sliced — batches can exceed 1000 records.

Raw upstream fields come through verbatim under jurisdiction_data. Default page size 100, max 1000. Per-country source codes, capabilities and caveats — call list_jurisdictions({jurisdiction:"<code>"}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jurisdictionYes'CZ' only.
sourceNoSource register code. Optional in list mode (if omitted, batches from all sources). REQUIRED in detail mode (when batch_id is provided).
batch_idNoBatch number (cisloDavky). If provided, switches to detail mode and returns the full list of change records. Requires `source`.
limitNoPage size. List mode: 1-100 (default 20). Detail mode: 1-1000 (default 100) — client-side slice of seznamNotifikaci.
offsetNoPagination skip. Applies to the batches array in list mode, or seznamNotifikaci in detail mode.
freshNoBypass cache.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queried_atYesISO-8601 + Europe/London timezone stamp for when the registry was queried.
jurisdictionNo
countNo
batchesNo
dataNo

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint: true, destructiveHint: false, idempotentHint: true. The description adds context beyond annotations: mentions the 501 error for non-CZ, explains pagination behavior (no total-count, client-side slicing, max 1000), and notes that upstream fields come verbatim under jurisdiction_data. No contradiction with annotations.

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?

The description is well-structured with clear sections for each mode, using bullet points and bold for emphasis. Every sentence adds value, and the length is appropriate for the complexity. It avoids repetition of schema details.

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?

Given the tool's complexity (two modes, multiple parameters, jurisdictional limitation, pagination behavior), the description covers all necessary aspects. Output schema exists, so return values are not required. The description is complete for an agent to select and use the tool correctly.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the two modes and how parameters interact (e.g., source required in detail mode, limit defaults differ). It provides practical guidance on pagination thresholds, which goes beyond the schema's field descriptions.

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 clearly states the tool's purpose: accessing the change-batch feed for CZ, listing or fetching change-notification batches. It distinguishes two modes (list and detail) and explicitly mentions the jurisdictional limitation (CZ only), differentiating it from sibling tools that do not operate on change batches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use each mode, including when to omit or provide batch_id. It also warns about the 501 error for other jurisdictions and directs users to call list_jurisdictions for per-country details, effectively preventing misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sophymarine/openregistry'

If you have feedback or need assistance with the MCP directory API, please join our Discord server