Skip to main content
Glama
il-opendata-mcp

il-opendata-mcp

by Shtibel1

Search data.gov.il datasets

search_datasets

Search the Israeli government open-data catalog by free-text query to find matching datasets and resource summaries; supports pagination for compact, focused results.

Instructions

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.

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": {
      "q": "<q>"
    },
    "name": "search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text search query, e.g. 'חברות ממשלתיות' or 'fuel stations'
rowsNoNumber of datasets to return (default 10, max 50)
startNoOffset for pagination (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does state the return shape: a compact list with titles, truncated notes, organizations, tags, resource summaries, and the count of resources with an active datastore. 'Truncated notes' is a useful non-obvious disclosure. It does not say whether auth is required or mention rate limits, though the catalog is presumably public.

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 sentences, front-loaded with the what and where, followed by the return shape and the alternative. No filler and no repetition 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?

There is no output schema, yet the description adequately explains what comes back, and all three parameters are documented in the schema. It is nearly complete for a simple three-parameter search tool; a note on result-set size or pagination would close the remaining gap.

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%, so q, rows and start are each fully documented with defaults and limits. The description adds no parameter-level meaning beyond the schema, so the baseline applies, but nothing is missing or misleading on the parameter side.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the Israeli government open-data catalog (data.gov.il CKAN package_search)') and describes what comes back. It routes the agent away from list_featured_datasets, but does not address the overlap with search_records, so the differentiation is only partial.

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 one explicit alternative-use rule: use list_featured_datasets for a curated starting point. That is real routing guidance rather than vague implication. It stops short of a full when/when-not statement, e.g. no guidance on paging through large result sets via start/rows.

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