Skip to main content
Glama
using76

BULC Building Designer

by using76
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

bulc_set_fds_thermocouple

Destructive

Configure furniture as FDS thermocouples to measure temperature at specific locations during fire simulations in BULC Building Designer.

Instructions

Configure a furniture item as an FDS thermocouple for temperature measurement. Used to record temperature at specific locations during simulation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID to configure as thermocouple
beadDiameterNoThermocouple bead diameter in mm. Default: 1.0
emissivityNoBead emissivity (0-1). Default: 0.9
deviceIdNoCustom device ID. Default: auto-generated

Implementation Reference

  • src/tools/fds-data.ts:402-408 (handler)
    Handler logic for the 'bulc_set_fds_thermocouple' tool: parses input arguments using Zod schema and sends a 'set_fds_thermocouple' command to the BULC client.
    case "bulc_set_fds_thermocouple": {
  const validated = SetThermocoupleSchema.parse(args);
  result = await client.sendCommand({
    action: "set_fds_thermocouple",
    params: validated,
  });
  break;
  • src/tools/fds-data.ts:335-340 (schema)
    Zod validation schema for the tool's input parameters.
    const SetThermocoupleSchema = z.object({
  furnitureId: z.string(),
  beadDiameter: z.number().positive().optional(),
  emissivity: z.number().min(0).max(1).optional(),
  deviceId: z.string().optional(),
});
  • src/tools/fds-data.ts:229-260 (schema)
    MCP tool definition including input schema, description, and annotations for 'bulc_set_fds_thermocouple'.
    {
  name: "bulc_set_fds_thermocouple",
  description:
    "Configure a furniture item as an FDS thermocouple for temperature measurement. " +
    "Used to record temperature at specific locations during simulation.",
  inputSchema: {
    type: "object" as const,
    properties: {
      furnitureId: {
        type: "string",
        description: "Furniture ID to configure as thermocouple",
      },
      beadDiameter: {
        type: "number",
        description: "Thermocouple bead diameter in mm. Default: 1.0",
      },
      emissivity: {
        type: "number",
        description: "Bead emissivity (0-1). Default: 0.9",
      },
      deviceId: {
        type: "string",
        description: "Custom device ID. Default: auto-generated",
      },
    },
    required: ["furnitureId"],
  },
  annotations: {
    readOnlyHint: false,
    destructiveHint: true,
  },
},
  • src/index.ts:84-94 (registration)
    Tool call routing in main MCP server handler: dispatches 'bulc_set_fds_thermocouple' and other FDS data tools to handleFdsDataTool.
    if (
  name === "bulc_get_fds_data" ||
  name === "bulc_set_fds_fire_source" ||
  name === "bulc_set_fds_detector" ||
  name === "bulc_set_fds_sprinkler" ||
  name === "bulc_set_fds_hvac" ||
  name === "bulc_set_fds_thermocouple" ||
  name === "bulc_clear_fds_data"
) {
  return await handleFdsDataTool(name, safeArgs);
}
  • src/index.ts:45-45 (registration)
    Inclusion of fdsDataTools (containing 'bulc_set_fds_thermocouple') into the global allTools list served via ListToolsRequest.
    ...fdsDataTools,      // 7 tools: get, fire_source, detector, sprinkler, hvac, thermocouple, clear

Tool Definition Quality

A4/5.0
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by describing a configuration action. The description adds valuable context about the tool's purpose in simulation recording, which isn't covered by annotations. No contradiction exists.

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?

Two sentences with zero waste: the first defines the action and purpose, the second provides usage context. Every word contributes to understanding without redundancy or fluff.

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?

For a destructive configuration tool with good annotations and full schema coverage, the description provides adequate context about what it does and why. The main gap is lack of output information (no output schema), but the description compensates somewhat by explaining the recording purpose.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description doesn't add any parameter-specific details beyond what's in the schema, so it meets the baseline but doesn't enhance understanding of the parameters.

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?

The description clearly states the specific action ('configure a furniture item as an FDS thermocouple') and the purpose ('for temperature measurement... during simulation'). It distinguishes from siblings by focusing on thermocouple configuration rather than other FDS elements like detectors, fire sources, or HVAC systems.

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

Usage Guidelines3/5

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

The description implies usage context ('during simulation') but doesn't explicitly state when to use this tool versus alternatives like 'bulc_set_fds_detector' or 'bulc_set_fds_fire_source'. It mentions the purpose but lacks explicit guidance on prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/using76/BULC_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server