Skip to main content
Glama
il-opendata-mcp

il-opendata-mcp

by Shtibel1

Get a data.gov.il dataset

get_dataset

Fetch metadata and resource summaries for a single Israeli government open-data dataset by CKAN name or UUID, including format, last_modified and datastore_active before querying records.

Instructions

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).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDataset name or UUID, e.g. 'gsa' or a package UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden; it does establish that this is a read-style fetch and discloses what the response contains (resource summaries with format, last_modified, datastore_active). However, it says nothing about behavior on a nonexistent/invalid id, whether resources are paginated or truncated, or any auth or rate-limit constraints.

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?

Two tight sentences: the first front-loads what is fetched and by what key, the second delivers the return-shape detail and the workflow dependency. No filler or restatement of the title.

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?

With no output schema, the description must sketch the return value, and it does at the right level: dataset metadata plus resource summaries with named fields. It omits error behavior and result-size limits, which is a minor gap for a single-record getter.

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 coverage is 100% and already gives an example ('gsa' or a package UUID), so the baseline would be 3. The description adds meaning by tying the parameter to CKAN semantics ('package name or UUID' via package_show), clarifying that either a human-readable slug or an identifier works.

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?

States a specific verb and resource ('Fetch metadata and resources for one dataset') and pins the identifier domain ('CKAN package name or UUID'), even naming the underlying API call (package_show). The singular 'one dataset by id' framing naturally separates it from search_datasets and search_records without needing to name them.

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

Usage Guidelines4/5

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

Gives a concrete downstream condition: check whether datastore_active is true before calling search_records, which is real routing guidance to a sibling. It does not state when NOT to use it (e.g. browsing by keyword should go to search_datasets), so it stops short of full when/when-not coverage.

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