Skip to main content
Glama

cz_get_act

Read-onlyIdempotent

Retrieve Czech legal act metadata by specifying the year and number. Access details from the e-Sbirka database for legal research.

Instructions

Fetch Czech act metadata by year and number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYese.g. ``2019``.
numberYese.g. ``110``.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
numberNo
eli_uriNo
citationNo
eli_noteNoeli_uri is the Czech national ELI IRI minted by the e-Sbirka open-data graph (opendata.eselpoint.gov.cz/esel-esb/eli/cz/sb/...). It follows the ELI URI template but is not a data.europa.eu-resolvable identifier; the human-readable page is on e-sbirka.gov.cz.
source_urlNo
dataset_noteNoe-Sbirka (the Czech Collection of Laws, Sbirka zakonu) is served as RDF via the opendata.eselpoint.gov.cz SPARQL endpoint (CC BY 4.0, ~92k acts, updated daily). Acts are addressed by year + number; the act IRI follows the ELI URI template (eli/cz/sb/{year}/{number}). cz_get_text returns the latest consolidated version's text, assembled from ordered HTML fragments - there is no single official XML/PDF file, so the text is reconstructed, not a verbatim document. Language: Czech.
version_dateNo
latest_version_uriNo
human_readable_citationNo
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds no behavioral traits beyond what is in annotations or schema. It is adequate but does not enhance transparency.

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?

A single, clear sentence that immediately conveys the tool's purpose. No wasted words.

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 simple input schema, output schema existence, and annotations covering behavioral safety, the description is complete enough for an agent to understand and invoke the tool correctly.

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 coverage is 100%, so baseline is 3. The description restates 'by year and number' but adds no additional meaning or constraints beyond the schema.

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 action (Fetch), resource (Czech act metadata), and identifiers (year and number). It distinguishes from siblings like cz_get_text and cz_search by specifying 'metadata'.

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?

The description implies usage when you have year and number, but does not explicitly state when to prefer this over siblings or provide exclusions. The sibling names hint at alternatives, but the description itself lacks guidance.

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/matematicsolutions/cz-eli-mcp'

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