Skip to main content
Glama

Israeli Real Estate and Legal Calculators

apostille country check

apostille_country_check
Read-only

Is a country (or territory) party to the Hague Apostille Convention in relation to Israel? Returns whether an Israeli document needs only an apostille or consular legalisation, based on the HCCH status table, including objections and territorial extensions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "apostille_country_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the result (default he)
countryYesCountry name in English or Hebrew

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is not burdened with safety disclosure. It still adds real value beyond them by naming the authoritative source (the HCCH status table) and warning that objections and territorial extensions are factored into the answer — behaviour an agent would not otherwise know.

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, both earning their place: the first states the question, the second states the answer shape and its data source. No preamble, no repetition of the tool name.

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?

With only two simple parameters and no output schema, the description supplies exactly what is missing: what the answer means (apostille vs consular legalisation), where it comes from, and what edge cases it accounts for. Nothing an agent needs before calling is absent.

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 description coverage is 100%, with both the country and the lang enum documented in-schema, so the baseline is 3. The description adds a little framing by scoping the query to a country or territory, but says nothing extra about accepted country-name forms or what the language switch affects.

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?

The description opens with a precise question-shaped verb+resource: whether a country or territory is party to the Hague Apostille Convention from Israel's perspective, and states the concrete answer returned (apostille vs consular legalisation). That is unmistakable and cannot be confused with any sibling (tax, court fees, warranties).

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 framing implies the use case — checking document legalisation requirements for Israeli documents — but there is no explicit when-to-use or when-not-to-use statement, no mention of prerequisites, and no named alternative. The context is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources