il-opendata-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_datasetsA | Search the Israeli government open-data catalog (data.gov.il CKAN package_search). Returns a compact list of matching datasets with titles, truncated notes, organizations, tags and resource summaries, including how many resources have an active datastore. Use list_featured_datasets for a curated starting point. |
| get_datasetA | Fetch metadata and resources for one dataset by CKAN package name or UUID (package_show). Resource summaries include format, last_modified and whether datastore_active is true (needed before search_records). |
| describe_resourceA | Return field names/types and the total record count for a CKAN datastore resource (datastore_search with limit 0). Fails with a clear error if the resource has no active datastore — use get_dataset to find resources where datastore_active is true. |
| search_recordsA | Query rows in a data.gov.il datastore resource (CKAN datastore_search). Supports full-text q, exact-match filters, field selection, limit (default 10, max 100) and offset. The resource must have an active datastore. |
| list_featured_datasetsA | Return a curated starting point of well-known data.gov.il datasets (companies, vehicles, education, fuel, government). This is not a complete index of the catalog — use search_datasets to find everything else. No network request is made. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool occupies a distinct stage of the workflow: catalog search (search_datasets), curated browsing (list_featured_datasets), metadata fetch (get_dataset), schema inspection (describe_resource), and row querying (search_records). Descriptions explicitly cross-reference each other to steer the agent (e.g. use list_featured_datasets vs search_datasets, check datastore_active via get_dataset before search_records).
All names follow a clean verb_noun snake_case pattern: search_datasets, get_dataset, describe_resource, search_records, list_featured_datasets. Resource nouns are used consistently (dataset vs resource vs records), matching the CKAN domain model.
Five tools is well-scoped for a read-only CKAN catalog server, covering the full discovery-to-query path without redundancy. Each tool earns its place and none feels like filler.
The core lifecycle (discover -> metadata -> schema -> query rows) is fully covered, including a clear failure path for non-datastore resources. Minor gaps: no organization/tag/group browsing tools and no way to fetch or download a resource's raw file when datastore_active is false.