Skip to main content
Glama

Project overview (what applies)

project_overview
Read-onlyIdempotent

For a project profile (use, city, stage and optional details): how many norms apply, which depend on missing data or need a specialist, the next permit actions with their legal source, and which questions would narrow the list most. Every omitted detail keeps norms in (over-inclusive by design).

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

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

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add behavior, and it does: every omitted detail keeps norms in, so results are deliberately over-inclusive and never silently exclude a norm. It also discloses that responses carry legal sources for permit actions. It stops short of saying anything about result size, ranking, or the specialist-escalation mechanism.

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?

A single dense sentence that front-loads the inputs and then lists the four output components, with the caveat after. No filler, but the output enumeration is packed into one clause chain and would read faster as a short list.

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 16-parameter read-only tool with no output schema, the description does the necessary work: it says what comes back (counts, missing-data dependencies, next actions with legal source, narrowing questions) and sets expectations that results are intentionally over-inclusive. Remaining gaps — result size, how roles partition the output, and the relationship to the sibling norm tools — are minor.

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 16 parameters, so the baseline is 3 and the schema does the heavy lifting. The description adds one cross-cutting semantic the schema only states piecemeal — that omitting any detail widens rather than narrows the norm set — but it adds nothing about the numeric threshold parameters (beds, storeys, floor_area, occupancy) that carry the most ambiguity.

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 names the resource (a project profile defined by use, city, stage and optional details) and enumerates the concrete outputs: how many norms apply, which depend on missing data or need a specialist, next permit actions with legal source, and narrowing questions. That is far more specific than the title, though it never names the sibling it is not (project_requirements, check_norm_for_project), so an agent still has to infer the boundary.

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?

Usage is implied rather than stated: you supply a partial project profile and get an applicability overview. There is no explicit when-to-use/when-not-to-use against project_requirements or check_norm_for_project, and no prerequisite such as 'call list_profile_options first for valid codes' (that only appears in the schema). The over-inclusion rule is the one genuine usage signal.

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.