Skip to main content
Glama
barvhaim

Israeli Land Authority MCP Server

by barvhaim

get_active_tenders

Retrieve currently open land tenders from the Israeli Land Authority to identify bidding opportunities for land development projects.

Instructions

Get all currently active land tenders

Returns a list of tenders that are currently open for submissions, useful for finding current bidding opportunities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main MCP tool handler for 'get_active_tenders', decorated with @mcp.tool(). It fetches active tenders via the API client, limits results, and returns a formatted dictionary response.
    @mcp.tool()
    def get_active_tenders(max_results: int = 100) -> Dict[str, Any]:
        """
        Get all currently active land tenders
    
        Returns a list of tenders that are currently open for submissions,
        useful for finding current bidding opportunities.
        """
        try:
            results = api_client.get_active_tenders()
    
            if isinstance(results, list):
                tender_list = results[:max_results]
            else:
                tender_list = results.get("results", results)[:max_results]
    
            return {
                "success": True,
                "count": len(tender_list),
                "active_tenders": tender_list,
            }
        except Exception as e:
            return {"success": False, "error": str(e)}
  • Supporting API client method in IsraeliLandAPI that implements the core logic for retrieving active tenders by calling search_tenders with active_only=True.
    def get_active_tenders(self) -> List[Dict[str, Any]]:
        """
        Get only active tenders
    
        Returns:
            List of active tenders
        """
        return self.search_tenders(active_only=True, page_size=10000)
  • Registration function that calls register_tender_tools(mcp, api_client), which defines and registers the get_active_tenders MCP tool via @mcp.tool() decorator.
    def register_tools(mcp, api_client):
        """Register all MCP tools"""
        register_tender_tools(mcp, api_client)
        register_settlement_tools(mcp, api_client)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool returns 'a list of tenders that are currently open for submissions', which clarifies the output behavior. However, it lacks details on permissions, rate limits, pagination (beyond the max_results parameter), or error handling, which are important for a tool with no annotation coverage.

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?

The description is appropriately sized and front-loaded: the first sentence states the core purpose, and the second adds context without redundancy. Both sentences earn their place by clarifying scope and utility, with zero wasted words.

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?

Given the tool's complexity (simple read operation), no annotations, and the presence of an output schema (which handles return values), the description is reasonably complete. It specifies the resource (land tenders), state (active), and purpose (finding bidding opportunities), though it could benefit from more behavioral details like permissions or limitations.

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?

The input schema has 1 parameter with 0% description coverage, and the tool description does not mention any parameters. Since the schema coverage is low, the description should compensate but fails to do so. The baseline is 3 because the schema provides some structure, but the description adds no parameter-specific information beyond what's implied by the tool's purpose.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get all currently active land tenders' specifies both the verb (get) and resource (land tenders). It distinguishes from siblings by focusing on 'active' tenders, though it doesn't explicitly contrast with tools like 'get_recent_results' or 'search_tenders'.

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

Usage Guidelines3/5

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

The description implies usage context: 'useful for finding current bidding opportunities' suggests when to use it. However, it doesn't provide explicit guidance on when to choose this tool over alternatives like 'search_tenders' or 'get_recent_results', nor does it mention any exclusions or prerequisites.

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/barvhaim/remy-mcp'

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