Skip to main content
Glama

Recent source changes

source_changes
Read-onlyIdempotent

What NORMOT's monitor detected in its sources (changed documents, expiring norms, latest Reshumot issues) and what was verified. With a profile, only documents relevant to that project.

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": "source_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
useNoUse code, or several comma-separated for a mixed building, e.g. residential or retail,office. See list_profile_options.
bedsNoNumber of beds, e.g. in a hotel, hospital or care home; used for thresholds in norms
cityNoMunicipality slug, e.g. tel-aviv, jerusalem. See list_profile_options.
roleNoShow the norms for one party, e.g. architect, developer, fire (fire safety consultant), authority: a role code from list_profile_options. Omit for all parties
siteNoComma-separated plot condition codes that apply; 'none' = checked and none apply; omit = not checked
roomsNoNumber of rooms; used for thresholds in norms
stageNoProject stage: feasibility (היתכנות ותכנון ראשוני), design (תכנון מפורט), permit (רישוי ובקשה להיתר), execution (ביצוע באתר), completion (גמר וטופס 4), operation (תפעול ותחזוקה). Omit = all stages
trackNoPermit track: standard, short or fast. Omit if unknown (no norm is excluded)
statusNonew = new building; existing = existing building
storeysNoNumber of storeys; used for thresholds in norms
featuresNoComma-separated project element codes from list_profile_options (features), e.g. pool; 'none' = checked and none apply; omit = not checked
occupancyNoNumber of occupants; used for occupancy thresholds in norms
floor_areaNoFloor area, m²; used for area thresholds in norms
height_classNoBuilding height class: low, high or multistory. Omit if unknown (no norm is excluded)
dwelling_unitsNoNumber of dwelling units (apartments)
building_heightNoBuilding height, m; used for height thresholds in norms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / properties / beds / description
      Added value: +"Number of beds, e.g. in a hotel, hospital or care home; used for thresholds in norms"
    • changedInput schema / properties / building_height / description
      Previous value: -"Building height, m"New value: +"Building height, m; used for height thresholds in norms"
    • addedInput schema / properties / dwelling_units / description
      Added value: +"Number of dwelling units (apartments)"
    • changedInput schema / properties / features / description
      Previous value: -"Comma-separated project element codes, e.g. pool; omit = not checked"New value: +"Comma-separated project element codes from list_profile_options (features), e.g. pool; 'none' = checked and none apply; omit = not checked"
    • changedInput schema / properties / floor_area / description
      Previous value: -"Floor area, m²"New value: +"Floor area, m²; used for area thresholds in norms"
    • changedInput schema / properties / height_class / description
      Previous value: -"Building height class"New value: +"Building height class: low, high or multistory. Omit if unknown (no norm is excluded)"
    • changedInput schema / properties / occupancy / description
      Previous value: -"Number of occupants"New value: +"Number of occupants; used for occupancy thresholds in norms"
    • changedInput schema / properties / role / description
      Previous value: -"Whose obligations to show, e.g. a role code from list_profile_options"New value: +"Show the norms for one party, e.g. architect, developer, fire (fire safety consultant), authority: a role code from list_profile_options. Omit for all parties"
    • addedInput schema / properties / rooms / description
      Added value: +"Number of rooms; used for thresholds in norms"
    • changedInput schema / properties / stage / description
      Previous value: -"Project stage"New value: +"Project stage: feasibility (היתכנות ותכנון ראשוני), design (תכנון מפורט), permit (רישוי ובקשה להיתר), execution (ביצוע באתר), completion (גמר וטופס 4), operation (תפעול ותחזוקה). Omit = all stages"
    • changedInput schema / properties / status / description
      Previous value: -"New building or existing building"New value: +"new = new building; existing = existing building"
    • addedInput schema / properties / storeys / description
      Added value: +"Number of storeys; used for thresholds in norms"
    • changedInput schema / properties / track / description
      Previous value: -"Permit track"New value: +"Permit track: standard, short or fast. Omit if unknown (no norm is excluded)"
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and external-source behavior are covered. The description adds that results come from a background monitor and can be scoped by project profile, but says nothing about freshness window, ordering, result volume, or what 'verified' status actually means — useful context is missing for a monitoring feed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the content inventory front-loaded and the profile-filter caveat second; nothing is redundant. The phrasing ('What NORMOT's monitor detected in its sources') is slightly indirect but still compact.

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?

With 16 optional parameters and no output schema, the description should do more to explain what comes back and how the many profile parameters interact with the change feed. It covers the gist (detected changes vs. verified items, profile-based narrowing) but leaves an agent unsure how to call it for a plain 'what's new' query without a profile.

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% across all 16 optional parameters, so the schema carries the per-parameter meaning and a baseline 3 applies. The description contributes one piece of extra semantics — that supplying profile parameters narrows results to that project — but it never says which parameters form a 'profile' or how they combine, so the added value is modest.

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

Purpose3/5

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

The description names the content types the feed carries (changed documents, expiring norms, latest Reshumot issues) and mentions verification status, which lets an agent guess this is a 'recent changes' digest. However, it has no clear verb+resource framing and never states what the tool actually returns (a list? a diff? counts?), so it is only loosely distinguishable from siblings like search_norms or project_requirements.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for overlapping needs (e.g. checking a single norm via get_norm). The only usage hint is the clause 'With a profile, only documents relevant to that project,' which implies a filtering mode but not when an agent should reach for this tool at all.

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.