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.

debim_urban_ingestA
Ingest OpenStreetMap (Overpass API) bounding box or GeoJSON string into native .debim urban manifest YAML.

Args:
    bbox: Optional bounding box [min_lat, min_lon, max_lat, max_lon]
    geojson_str: Optional GeoJSON FeatureCollection string
    crs_epsg: Metric UTM CRS code (default 32647 for Thailand WGS84/UTM Zone 47N)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.3/5.0

Scored across 7 tools

Disambiguation4/5

Each tool maps to a distinct pipeline stage (ingest, validate, qto, cost, template, compile, viewer), so an agent can mostly tell them apart. The only mild overlap is between debim_qto (quantity take-off) and debim_cost (BOQ priced from those quantities), and between debim_cost and debim_cost_template, but descriptions clarify the boundary.

Naming Consistency4/5

All tools share a predictable debim_ prefix with a single domain term following. The verb style varies a bit (ingest, compile, cost, generate, validate, qto), with some being nouns rather than verbs, but the naming is consistently readable and scoped.

Tool Count5/5

Seven tools is well-scoped for a BIM/urban pipeline, each earning its place as a distinct stage. No bloat and no single trivial wrapper.

Completeness4/5

The surface covers a coherent end-to-end flow: ingest, validate, quantity take-off, cost estimation, template generation, IFC compilation, and 3D viewing. Minor gaps exist, such as no explicit manifest load/edit/export tooling and no post-cost reporting beyond CSV, but core workflows are covered.

Maintenance

ActivityNo data
ResponsivenessResponsive

Resources