Skip to main content
Glama
barvhaim

Israeli Land Authority MCP Server

by barvhaim

get_tender_details

Retrieve comprehensive tender information including dates, guarantees, documents, and administrative details from the Israeli Land Authority by specifying a tender ID.

Instructions

Get comprehensive details for a specific tender by ID

Returns detailed information including dates, guarantees, documents, and administrative details for the specified tender.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function implementing get_tender_details. It uses TenderDetailsArgs input and delegates to the API client.
    @mcp.tool()
    def get_tender_details(args: TenderDetailsArgs) -> Dict[str, Any]:
        """
        Get comprehensive details for a specific tender by ID
    
        Returns detailed information including dates, guarantees, documents,
        and administrative details for the specified tender.
        """
        try:
            details = api_client.get_tender_details(args.michraz_id)
            return {"success": True, "tender_id": args.michraz_id, "details": details}
        except Exception as e:
            return {"success": False, "error": str(e), "tender_id": args.michraz_id}
  • Pydantic BaseModel defining the input schema for the get_tender_details tool, requiring a single michraz_id integer.
    class TenderDetailsArgs(BaseModel):
        """Arguments for tender details tools"""
    
        michraz_id: int = Field(..., description="The tender ID to get details for")
  • Registration call in the main server setup that triggers tool registration, including get_tender_details via register_tender_tools.
    register_tools(mcp, api_client)
  • Underlying API client method that performs the HTTP GET request to the Israeli Land Authority API to retrieve tender details.
    def get_tender_details(self, michraz_id: int) -> Dict[str, Any]:
        """
        Get detailed information for a specific tender
    
        Args:
            michraz_id: The tender ID to get details for
    
        Returns:
            Dictionary containing tender details
        """
        self._rate_limit()
    
        try:
            response = self.session.get(
                f"{self.BASE_URL}/MichrazDetailsApi/Get",
                params={"michrazID": michraz_id},
                timeout=30,
            )
            response.raise_for_status()
            return response.json()
        except requests.exceptions.RequestException as e:
            raise Exception(
                f"Failed to get tender details for ID {michraz_id}: {str(e)}"
            )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool 'Returns detailed information' and lists some data types (dates, guarantees, documents, administrative details), but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or whether it's a read-only operation. The output schema exists, but the description doesn't hint at response structure beyond the listed categories.

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 efficiently structured in two sentences: the first states the core purpose, and the second elaborates on return values. Every phrase adds value without redundancy, and it's front-loaded with the key action ('Get comprehensive details').

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

Completeness3/5

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

Given the tool's moderate complexity (single parameter, no annotations, but with an output schema), the description is partially complete. It covers the basic purpose and return categories, but lacks usage guidelines, behavioral details, and deeper parameter context. The output schema mitigates some gaps, but the description should do more to compensate for missing annotations.

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?

The description adds meaningful context beyond the input schema, which has 0% description coverage. It clarifies that the tool requires 'a specific tender by ID', implicitly explaining the 'michraz_id' parameter's purpose as a unique identifier. However, it doesn't detail parameter constraints (e.g., ID format or range) or provide examples.

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 with a specific verb ('Get') and resource ('comprehensive details for a specific tender by ID'), distinguishing it from siblings like 'get_active_tenders' or 'search_tenders' that handle multiple tenders. However, it doesn't explicitly differentiate from 'get_tender_map_details', which might be a similar single-tender lookup tool.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_active_tenders' or 'search_tenders'. It mentions 'by ID' but doesn't clarify prerequisites (e.g., needing a known tender ID) or exclusions (e.g., not for searching by other criteria).

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