Skip to main content
Glama
DavidOsherdiagnostica

Data.gov.il MCP Server

search_records

Search across government datasets with free-text queries, filters, and pagination. Retrieve specific fields and sort results for precise data extraction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across all fields. Supports Hebrew/English, partial matches, and multiple words. Examples: 'תל אביב', 'בנק לאומי', 'emergency'
sortNoSort results by one or more fields. Format: ["field_name asc/desc"]. Examples: ["Name asc"], ["Date desc", "Amount desc"]
limitNoNumber of results to return (1-1000). Use 5-10 for quick exploration, 20-50 for analysis, 100-1000 for comprehensive data extraction
fieldsNoReturn only specific fields to reduce response size and improve performance. Examples: ["Name", "City"], ["Amount", "Date", "Type"]
offsetNoSkip first N results for pagination. Use with limit for paging: page 1: offset=0, page 2: offset=limit, page 3: offset=limit*2
filtersNoExact field matches as JSON object. Supports single values, arrays, and operators. Examples: {"City": "תל אביב"}, {"City": ["תל אביב", "חיפה"]}, {"Amount": {"$gte": 1000}}
distinctNoReturn unique values for a specific field only (no full records). Useful for getting all possible values. Examples: 'City', 'Type', 'Status'
resource_idYesResource UUID from list_resources. Get this ID from datastore_active=true resources. Example: '2202bada-4baf-45f5-aa61-8c5bad9646d3' for bank branches
include_totalNoInclude total count of matching records in response. Essential for pagination planning and showing 'X of Y results'
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/DavidOsherdiagnostica/data-gov-il-mcp'

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