Tendy - Israeli public tenders

List tender collections

list_collections

Read-onlyIdempotent

List the Tendy hub pages that browse_collection opens, each with the kind and key to pass, its link and current counts. Without kind: an overview of the government and municipal pages, every region, and the publishing bodies and main categories with the most tenders. With kind: up to 40 pages of that kind, busiest first; name narrows them by part of a Hebrew name, for example a publishing body or a subcategory. Only pages with public procurement tenders are listed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_collections"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	category (what is being bought), publisher (one publishing body), region (an Israeli district), government (all government bodies) or municipal (all local authorities).
`name`	No	Part of a Hebrew name, to narrow the list.

Output Schema

Name	Required	Description	Default
`notice`	Yes
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), yet the description still adds real behavior: a 40-item cap, busiest-first ordering for kind queries, substring narrowing by Hebrew name, and the inclusion filter that only pages with public procurement tenders appear. It does not describe pagination beyond the cap or any empty-result behavior, which keeps it short of a 5.

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?

Three dense sentences, front-loaded with what is returned and then the two parameter regimes; nothing is filler. The opening sentence is long and packs return-field detail, but every clause contributes to correct invocation.

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?

For a two-parameter read-only listing tool with a full output schema and full enum documentation, the description covers the remaining unknowns: what a result row contains, how kinds change the result, ordering, the cap, and the tender-only inclusion rule. Nothing an agent needs to call it correctly is missing.

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% and the enum values are already documented, so the baseline is met by the schema alone. The description adds genuine meaning on top: kind's absence produces a cross-kind overview, its presence produces a sorted capped slice, and name is specifically a fragment of a Hebrew name such as a publisher or subcategory.

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?

States a concrete verb and resource ("List the Tendy hub pages") and immediately ties them to a sibling by explaining that these are the pages browse_collection opens, with each item carrying the kind/key needed for that call. An agent can distinguish this listing tool from browse_collection and list_categories without opening any schema.

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 explicit conditional guidance: with no kind you get an overview (government, municipal, all regions, top publishers and categories); with kind you get up to 40 pages of that kind, busiest first. It lacks an explicit "use X instead when..." exclusion against list_categories, but the usage context is clear enough to act on.

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

All Tendy - Israeli public tenders tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.