Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Find the most-extreme element by geometry

find_extreme
Read-onlyIdempotent

Find the largest, smallest, or northmost/southmost/eastmost/westmost elements by category or level, then use returned external IDs to highlight or zoom to them.

Instructions

Find the most-extreme element(s) by position or size.

Use this to answer superlative questions (e.g. "the largest piece of equipment", "the northmost air handler", "the smallest transformer"), then pass the returned external_ids to highlight_elements or zoom_to. This tool does NOT change the view by itself.

For largest/smallest, each element carries its volume_cuft. For compass directions the answer is simply which element is most extreme.

Examples: - Largest equipment: op='largest' - Northmost air handler: op='northmost', category='air_handlers' - Three smallest fans: op='smallest', category='fans', limit=3

Returns: {"op": str, "count": int, "elements": [{external_id, asset_type, description, level_name, volume_cuft?}]} ranked most-extreme first.

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": {
      "op": "<op>"
    },
    "name": "find_extreme"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesWhich extreme: a compass direction (northmost/southmost/eastmost/westmost) ranks by position; largest/smallest ranks by 3D bounding-box volume.
levelNoOptional building level to restrict to. Omit for all levels.
limitNoHow many ranked elements to return (1-50). Use 1 for the single most-extreme element.
categoryNoOptional category to restrict to (e.g. the largest air handler). Omit to rank across all tracked equipment.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds genuine context beyond them: the view is not modified, largest/smallest ranks by 3D bounding-box volume, and results are ranked most-extreme first. It does not discuss empty-result behavior or permission requirements, keeping it below a 5.

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?

Front-loaded purpose sentence, then usage, then a compact bulleted example list. Every section is scannable and the examples earn their space by demonstrating parameter combinations.

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?

Fully covers when to call and what the result means; the explicit Returns block is partly redundant given an output schema exists, but it clarifies ranking order and the optional volume_cuft field, so no information an agent needs is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value with worked examples pairing op values with category and limit (e.g. op='smallest', category='fans', limit=3), showing how the parameters combine for real queries.

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 ('find the most-extreme element(s) by position or size') and scopes it to superlative queries, which distinguishes it from the sibling find_* tools that filter or search rather than rank.

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

Usage Guidelines5/5

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

Explicitly says when to use it (superlative questions), gives concrete example phrasings, names the downstream tools (highlight_elements, zoom_to), and states an exclusion: 'This tool does NOT change the view by itself.'

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