Skip to main content
Glama

Israel Tenders

by io.github.pipeworx-io
OverviewAdmin

Israel Search Tenders

israel_search_tenders
Read-onlyIdempotent

Search Israeli government competitive tenders (מכרזים) from the official Government Procurement Administration dataset on data.gov.il. Returns each tender's publication number, name, publishing ministry and unit, procedure type, status, publication/closing dates, winning supplier, and subject area. Pass a free-text query (Hebrew or matching text) to filter, e.g. "בריאות" (health) or a ministry name; 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, subject, or supplier name. 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": 50,
+    "offset": 0,
+    "query": "משרד ההגנה"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds details about return fields, source, and pagination. No contradiction.

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, each dense with information. First sentence covers purpose and output, second covers usage. No filler words.

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

Completeness5/5

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

Without output schema, description comprehensively enumerates returned fields. Explains pagination parameters and usage. Complete for a search tool.

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 has 100% coverage for all 3 parameters. Description adds context: query is optional, examples given, and explains browsing behavior. Enhances understanding beyond schema.

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?

Clearly states verb 'Search', resource 'tenders', and specifies the official dataset source. Distinguishes from sibling tool 'israel_search_exemptions' by name and context.

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 explicit usage guidance: pass a free-text query (Hebrew or matching text) to filter, or omit to browse recent records. Includes examples. Does not mention when not to use or compare to siblings.

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