Skip to main content
Glama
il-opendata-mcp

il-opendata-mcp

by Shtibel1

Search datastore records

search_records

Query rows from an active data.gov.il CKAN datastore resource using full-text search, exact-match filters, field selection, limit, and offset for paginated record retrieval.

Instructions

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.

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": {
      "resource_id": "<resource_id>"
    },
    "name": "search_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFull-text search across the datastore
limitNoNumber of records to return (default 10, max 100)
fieldsNoOptional list of field names to return
offsetNoOffset for pagination (default 0)
filtersNoExact-match field filters, e.g. { "STATUS": "פעיל" }
resource_idYesCKAN resource UUID with datastore_active=true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the default page size (10) and cap (100) plus the active-datastore prerequisite, but says nothing about result shape, total-count metadata, failure behavior on a non-datastore resource, or authentication/rate limits.

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, with the operation and resource scope front-loaded before the capability list and the prerequisite. Nothing is padded or redundant enough to slow an agent down.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, no-output-schema tool, the definition covers the inputs and one prerequisite but omits what comes back (records array, total count) and how pagination terminates. That gap matters because there is no output schema to fill it.

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 q, filters, fields, limit, and offset are already documented in the schema, including the filter example. The description restates the same set without adding syntax or semantics beyond what the schema provides; baseline 3 applies.

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 — query rows inside a data.gov.il datastore resource — and even names the underlying CKAN operation (datastore_search). The 'resource' scope implicitly separates it from search_datasets/get_dataset, but no sibling is named explicitly.

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?

Gives one real precondition (the resource must have an active datastore, i.e. datastore_active=true), which steers the agent toward describe_resource first. However, it never states when to prefer this over search_datasets or how to handle pagination strategy, so usage is only implied.

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