Skip to main content
Glama
PRIDA-TAKON

debim

by PRIDA-TAKON
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
debim_validateB

Validate a declarative BIM manifest YAML string. Checks schema syntax, grid consistency, storey heights, and material references.

debim_qtoC

Calculate Quantitative Take-Off (QTO) material quantities deterministically. Returns exact concrete volume (m3), formwork area (m2), rebar weight (kg), structural steel (kg), timber volume (m3), masonry area (m2), and excavation (m3).

debim_cost_templateC

Generate a minimal project-scoped price catalog YAML template based only on the materials and items actively used by the building model.

debim_costB
Calculate full Bill of Quantities (BOQ) and cost estimation.
Matches QTO quantities against unit material and labor prices.
If prices_yaml is omitted, auto-generates a benchmark template.
Optionally exports the complete BOQ to a CSV file.
debim_compile_ifcC

Compile a declarative BIM YAML manifest into a standard IFC4 building model.

debim_generate_viewerB

Generate a standalone, zero-dependency interactive 3D HTML web viewer with OrbitControls, X-Ray, Section Cut, and Layer Explorer.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct stage of the BIM pipeline (validate, QTO, cost template, cost, IFC compile, viewer), so most selections are unambiguous. The only mild overlap is between debim_cost_template (generates a price catalog YAML) and debim_cost (which can auto-generate a benchmark template when prices are omitted), but descriptions clarify the distinction.

Naming Consistency5/5

All six tools use a consistent snake_case pattern with the same debim_ prefix and clear action-oriented verbs (validate, qto, cost_template, cost, compile_ifc, generate_viewer). There are no mixed conventions or vague verbs.

Tool Count5/5

Six tools is well-scoped for a declarative BIM manifest pipeline: validate, quantify, cost, compile, and visualize. Each tool earns its place, and there are no redundant or filler operations.

Completeness4/5

The surface covers a full workflow from validation through QTO, cost estimation, IFC compilation, and viewer generation, with no dead ends for the stated purpose. Minor gaps exist, such as no explicit manifest editing/update helper or reverse import from IFC, but these are workable given the declarative input model.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources