Skip to main content
Glama
Sign In

NORMOT — Israeli building norms

by io.github.danvolsky-source
OverviewDiscussionsAdmin

Search norms

search_norms
Read-onlyIdempotent

Search Israeli building and planning norms by Hebrew words (substring search over norm texts, sections and document titles; norms in force come first). Returns norms with their permanent URL; call get_norm for the full text and citation.

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": {
      "query": "<query>"
    },
    "name": "search_norms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many norms to return, 1–20
queryYesHebrew search words, e.g. מעקה, ממ"ד, רוחב מדרגות
offsetNoFor the next page; at most 100 (no bulk export)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many norms to return, 1–20"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new behavior: substring (not exact or semantic) matching, the ranking rule that in-force norms come first, and that results carry a permanent URL. It does not mention result shape beyond the URL or how empty results behave.

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, front-loaded with the verb, resource, and matching semantics, then the follow-up call. No filler and no repetition of schema bounds.

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 three-parameter read-only search with no output schema, the description covers what is returned (norms with permanent URL) and what to do next. The only gap is that it does not describe the result fields beyond the URL, which is minor given the absence of an output schema.

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%, so query, limit, and offset are already documented with examples and bounds. The description reinforces that the query is Hebrew words and that matching is substring-based, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 ('Search Israeli building and planning norms') plus the exact matching scope: substring search over norm texts, sections, and document titles. It also names the sibling it is not (get_norm) and the ordering rule, so an agent can distinguish it from get_norm without opening either 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?

Explicitly routes the agent onward: 'call get_norm for the full text and citation,' which tells the agent this tool is a discovery step, not a retrieval step. It does not state when to prefer check_norm_for_project or project_requirements, so the sibling routing is only partially covered.

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

All NORMOT — Israeli building norms toolsInspect
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.

Resources