Skip to main content
Glama
BIM Viewer MCP Server

BIM Viewer MCP Server

Count or cost-total work orders

find_workorders
Read-onlyIdempotent

Count maintenance work orders or total their costs by level, status, priority, failure class, and equipment category for building maintenance reporting.

Instructions

Count or cost-total maintenance work orders under fixed filters.

Use this for work-order / maintenance questions, e.g. "how many work orders on Level 2", "open work orders", "high-priority work orders on the 1st floor that service the heat pumps", "how much have we spent on HVAC work orders". All filters are optional and combine with AND.

Examples: - Work orders on Level 1: level='Level 1' - Open work orders: status='OPEN' - High-priority WSHP on Level 1: level='Level 1', asset_category='heat_pumps', priority='high' - HVAC maintenance spend: failure_class='HVAC', measure='cost'

Returns (count): {"measure": "count", "filters": {...}, "count": int, "breakdown_by_status": {status: int}}. Returns (cost): {"measure": "cost", "filters": {...}, "count": int, "total_cost": float, "total_labor_hours": float, "avg_cost": float}.

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

Input Schema

NameRequiredDescriptionDefault
levelNoOptional building level to restrict to. Omit for all levels.
statusNoOptional work-order status (e.g. OPEN for open work orders).
measureNo'count' (default) returns how many plus a status breakdown; 'cost' returns spend/labor totals (total_cost, total_labor_hours, avg_cost).count
priorityNoOptional priority as a word: high (most urgent), normal, or low.
failure_classNoOptional failure class (the system the work order is against).
asset_categoryNoOptional category of the equipment a work order services (e.g. 'heat_pumps' = the WSHP units).
reported_by_roleNoOptional role that reported the work order.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds genuine behavioral context beyond them: that all filters are optional and combine with AND, and what each measure returns — exactly the kind of aggregation semantics annotations cannot express.

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 one-line purpose, then usage examples, then return shapes — each block serves a distinct need. The example list is compact and each entry demonstrates a different filter dimension rather than padding.

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?

With 7 optional parameters, an enum-heavy schema, and an output schema present, the definition covers what an agent needs: the AND-combination rule, worked examples for ambiguous natural-language phrasings, and a summary of both return shapes. Nothing required for correct invocation 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; the description earns above that by demonstrating how filters compose in practice (e.g. level + asset_category + priority together) and by tying measure='cost' to spend/labor questions. It clarifies combined-filter intent rather than restating individual field docs.

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 pair and resource — 'Count or cost-total maintenance work orders' — plus the scoping constraint ('under fixed filters'), so the agent knows exactly what operation and domain this covers. The two modes (count vs. cost) are named in the first line, distinguishing it from any listing/retrieval sibling.

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 tells the agent to use it 'for work-order / maintenance questions' and supplies four natural-language question examples that map to concrete invocations. It does not name an alternative tool or state when NOT to use it, which keeps it short of a 5.

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