Skip to main content
Glama
il-opendata-mcp

il-opendata-mcp

by Shtibel1

List curated featured datasets

list_featured_datasets

Get a curated list of well-known data.gov.il datasets by category (companies, vehicles, education, fuel, government) as a starting point; use search to find others.

Instructions

Return a curated starting point of well-known data.gov.il datasets (companies, vehicles, education, fuel, government). This is not a complete index of the catalog — use search_datasets to find everything else. No network request is made.

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_featured_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional category filter: companies, vehicles, education, fuel, government, or allall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it discloses two non-obvious traits: the result set is curated/incomplete and 'No network request is made,' implying static, possibly non-live content. It stops short of describing the shape of returned entries or whether the list can become stale, which would matter for a bundled snapshot.

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?

Three short sentences, zero waste: scope first, exclusion second, behavioral note last. Everything is front-loaded and each sentence carries distinct information.

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 single-optional-param read tool with no output schema and no annotations, the description covers scope, the sibling alternative, and the no-network/no-completeness caveats. A brief note on what each returned dataset entry contains would close the remaining gap.

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% with an enumerated category parameter and a documented default of 'all', so the schema already does the work. The description echoes the category names but adds no filtering semantics beyond what the schema states.

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 specific verb and resource ('Return a curated starting point of well-known data.gov.il datasets') and enumerates the covered topics (companies, vehicles, education, fuel, government). It explicitly marks itself as a curated subset rather than the full catalog, which cleanly separates it from search_datasets.

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

Usage Guidelines5/5

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

Gives an explicit when-not and names the alternative: 'This is not a complete index of the catalog — use search_datasets to find everything else.' The agent knows exactly when to fall through to the search tool instead of this one.

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