Skip to main content
Glama

Fetch a CZ-specific source-register record

get_specialised_record
Read-onlyIdempotent

Retrieve sector-specific data from Czech ARES specialised registers (e.g., ros, res, rzp, nrpzs, rpsh, rcns, szr, rs, ceu) for an IČO, returning the full upstream record. Use when basic company profile lacks required fields like trade licences, school accreditations, or healthcare facility lists.

Instructions

Retrieve a record from one of ARES's specialised source registers — covers sector-specific data the basic profile doesn't include.

── CZ (Czechia ARES) ── Available source codes: • ros — Public Registers (Registr osob) summary state • res — Statistical Register of Economic Entities (Registr ekonomických subjektů) • rzp — Trade Licence Register (Registr živnostenského podnikání) — trade licences a sole trader / company holds • nrpzs — National Register of Healthcare Providers (Národní registr poskytovatelů zdravotních služeb) — for hospitals, clinics, pharmacies • rpsh — Register of Political Parties and Movements (Registr politických stran a hnutí) • rcns — Register of Churches and Religious Societies (Registr církví a náboženských společností) • szr — Farmers' Register (Registr zemědělských podnikatelů) • rs — Register of Schools (Registr škol) • ceu — Central Insolvency Record (Centrální evidence úpadců)

Each source returns its own response shape — refer to ARES API docs at https://ares.gov.cz/swagger-ui/ for field details. The full upstream record is returned verbatim under record. Use this when the basic get_company_profile or get_officers/get_psc/get_charges don't have the field you need (e.g. trade-licence specialisations for sole traders → rzp, school accreditation details → rs, healthcare facility list → nrpzs). Returns 404 if the IČO doesn't exist in that specific source register. Pricing: free.

Other jurisdictions return 501.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jurisdictionYes'CZ' or 'CH'.
sourceYesSource register code (lowercase). CZ: ros/res/rzp/nrpzs/rpsh/rcns/szr/rs/ceu. CH: sogc (SOGC publication by ID), sogc_bydate (YYYY-MM-DD), registry_by_commune (BFS community ID).
company_idYesFor CZ: 8-digit IČO. For CH: SOGC publication ID (sogc), date YYYY-MM-DD (sogc_bydate), or BFS community ID (registry_by_commune).
freshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queried_atYesISO-8601 + Europe/London timezone stamp for when the registry was queried.
jurisdictionNo
record_kindNo
recordNo
jurisdiction_dataNoFull original response fields from the upstream registry, field names unchanged. Shape is jurisdiction-specific — see `list_jurisdictions({ jurisdiction: '<CODE>' })`.
Behavior4/5

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

Annotations already set readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. Description adds valuable context: returns full upstream record verbatim, 404 for missing IČO in source, 501 for non-CZ jurisdictions, and free pricing. No contradictions.

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?

Well-structured with clear headings for CZ section, but could be more concise by using a bullet list instead of paragraph for source codes. However, content is front-loaded and each sentence adds value.

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 (multiple jurisdictions, many source codes, varying record shapes) and the presence of an output schema, the description provides comprehensive guidance: lists all sources with explanations, clarifies authentication (pricing: free), return behavior, and when to use alternatives. No gaps.

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 has 75% description coverage; description adds meaning for source parameter by listing all CZ source codes and their purposes, and clarifies company_id formats per jurisdiction. For fresh, description doesn't add beyond schema. Overall, the description compensates for incomplete schema 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?

Description clearly states 'Retrieve a record from one of ARES's specialised source registers' with specific verb and resource. It distinguishes from siblings like get_company_profile and get_officers by highlighting that it covers sector-specific data the basic profile doesn't include.

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?

Explicitly tells when to use this tool ('Use this when the basic get_company_profile or get_officers/get_psc/get_charges don't have the field you need') and provides examples for specific sources. Also mentions when to expect 404 or 501, giving clear guidance on limitations.

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