Skip to main content
Glama

Israel Tenders

by io.github.pipeworx-io
OverviewAdmin

Israel Search Exemptions

israel_search_exemptions
Read-onlyIdempotent

Search Israeli government exemption contracts and non-competitive procurement (התקשרויות בפטור והליכים תחרותיים) from the official Government Procurement Administration dataset on data.gov.il. Returns each contract's publication number, name, publishing ministry and unit, exemption regulation (תקנה), status, decision essence, approver, dates, supplier, monetary amount, currency, and subject. Pass a free-text query (Hebrew or matching text) to filter; omit to browse the most recent records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax records to return (default 20, max 100).
queryNoFree-text search across all fields (Hebrew works best), e.g. a ministry, supplier, or subject. Omit to browse.
offsetNoNumber of records to skip for pagination (default 0).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 20,
+    "query": "רפואה"
+  },
+  {
+    "limit": 100,
+    "offset": 0,
+    "query": "משרד הבריאות"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint (all true/not destructive). The description adds value by listing the specific data source and return fields, but does not contradict annotations.

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

Conciseness4/5

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

The description is concise (two sentences) and front-loaded with the main action and data source. It includes necessary return field enumeration, making it informative without being verbose.

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?

For a read-only search tool with no output schema, the description covers the data source, return fields, and usage patterns. It is complete enough for correct invocation, though pagination details are left to the schema.

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% (all 3 parameters described). The description adds context for the query parameter ('omit to browse') but mostly reiterates schema info. Baseline 3 is appropriate.

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?

The description clearly states the tool searches Israeli government exemption contracts from a specific dataset (Government Procurement Administration on data.gov.il). It distinguishes itself from siblings like 'israel_search_tenders' by focusing on exemptions versus tenders.

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?

Provides clear guidance: use a free-text query to filter or omit to browse recent records. It implicitly differentiates from related siblings (e.g., israel_search_tenders) via the tool name and focus, but no explicit when-not-to-use instruction.

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

All Israel Tenders toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources