Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Find elements by cost

find_elements
Read-onlyIdempotent

Find building elements by replacement or maintenance cost and return external IDs for cost analysis; use the results to highlight or isolate elements in the BIM model.

Instructions

Find building elements by a cost criterion; return their externalIds.

Use this to answer cost questions, then pass the returned external_ids to highlight_elements (to show them in place) or isolate. This tool does NOT change the view by itself.

Examples: - Ten most expensive: metric='replacement_cost', op='top', limit=10 - Over $50,000: metric='replacement_cost', op='gt', value=50000 - Highest maintenance: metric='maintenance_cost', op='top', limit=5

Returns: {"metric": str, "count": int, "elements": [{external_id, asset_type, description, metric_value}]}.

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

Input Schema

NameRequiredDescriptionDefault
opYesHow to select: 'top' for the highest-cost N; gt/gte/lt/lte to compare against a dollar threshold.
limitNoMax elements to return (1-500). For op='top' this is N.
valueNoDollar threshold for gt/gte/lt/lte. Ignored when op='top'.
metricYesWhich cost to rank/filter by: an asset's replacement_cost, or its summed maintenance_cost from work orders.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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/openWorld, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: it mutates nothing in the view, it emits external_ids intended as input to other tools, and it spells out the response payload including per-element metric_value.

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?

Front-loaded one-liner followed by usage, compact examples, and a return shape — easy to scan and nothing is buried. The Returns block partly restates the existing output schema, a minor redundancy that keeps it from a 5.

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?

For a 4-parameter query tool with a full output schema and rich annotations, nothing an agent needs is missing: selection semantics, the follow-up tool chain, realistic invocation examples, and the response shape are all present.

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% and enum values plus the 'value ignored when op=top' rule are already in the schema, so the baseline is 3. The worked examples do add practical meaning by pairing metric/op/limit/value in recognizable query shapes, which is worth slightly more than the floor but not a full extra level.

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 building elements by a cost criterion'), the scoping axis (cost), and the return value (externalIds). The cost-based scope is enough to distinguish it from category/room/clearance finders in the sibling list without opening the 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 says to use it for cost questions and what to do next with the results — pass external_ids to highlight_elements or isolate — and warns that the tool does not change the view by itself. It lacks an explicit exclusion versus alternative finders (e.g. a generic extreme-value finder), so it stops short of full when-not guidance.

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