Skip to main content
Glama
using76
by using76

bulc_list_rooms

Read-only

Retrieve all rooms with IDs, names, positions, and dimensions for modify/delete operations in BULC Building Designer. Filter by floor level to view specific rooms.

Instructions

Get a list of all rooms with their IDs, names, positions, and dimensions. Use the returned IDs for modify/delete operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoFilter by floor level index. Omit to list all rooms.

Implementation Reference

  • Specific handler case for 'bulc_list_rooms' tool: validates input using ListRoomsSchema and sends 'list_rooms' command to BULC client.
    case "bulc_list_rooms": {
      const validated = ListRoomsSchema.parse(args);
      result = await client.sendCommand({
        action: "list_rooms",
        params: validated,
      });
      break;
    }
  • src/index.ts:69-71 (registration)
    Routing registration in main MCP server handler: dispatches all 'bulc_*_room' tools (including bulc_list_rooms) to handleRoomTool.
    if (name.startsWith("bulc_") && name.includes("room")) {
      return await handleRoomTool(name, safeArgs);
    }
  • Tool definition object for 'bulc_list_rooms' including name, description, inputSchema, and annotations (part of roomTools array).
    {
      name: "bulc_list_rooms",
      description:
        "Get a list of all rooms with their IDs, names, positions, and dimensions. " +
        "Use the returned IDs for modify/delete operations.",
      inputSchema: {
        type: "object" as const,
        properties: {
          level: {
            type: "integer",
            description: "Filter by floor level index. Omit to list all rooms.",
          },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • Zod schema for input validation of 'bulc_list_rooms' parameters.
    const ListRoomsSchema = z.object({
      level: z.number().int().optional(),
    });
  • src/index.ts:40-51 (registration)
    Inclusion of roomTools (containing bulc_list_rooms schema) in the allTools array, used for listing available tools in MCP server.
    const allTools = [
      ...contextTools,      // 8 tools: spatial context, home info, levels, undo/redo, save
      ...roomTools,         // 5 tools: create, create_polygon, list, modify, delete
      ...wallTools,         // 5 tools: create, create_rectangle, list, modify, delete
      ...furnitureTools,    // 5 tools: catalog, place, list, modify, delete
      ...fdsDataTools,      // 7 tools: get, fire_source, detector, sprinkler, hvac, thermocouple, clear
      ...meshTools,         // 5 tools: list, create, auto, modify, delete
      ...simulationTools,   // 4 tools: get_settings, time, output, ambient
      ...fdsRunTools,       // 6 tools: preview, validate, export, run, status, stop
      ...resultTools,       // 5 tools: open_viewer, list_datasets, point_data, aset, report
      ...evacTools,         // 25 tools: setup, stairs, agents, run, results, advanced features
    ];
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds useful context about the return format (IDs, names, positions, dimensions) and the purpose of IDs for subsequent operations, which goes beyond annotations. However, it doesn't disclose behavioral traits like pagination, rate limits, or error conditions.

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?

The description is two sentences, front-loaded with the core purpose and followed by a usage note. Every word adds value without redundancy, making it efficiently structured and easy to parse.

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?

Given the tool's simplicity (one optional parameter, read-only, no output schema), the description is largely complete. It covers the purpose, return data, and usage context. A 5 is reserved for tools with more complexity that require additional disclosures (e.g., side effects), which isn't needed here.

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%, with the parameter 'level' fully documented in the schema as an optional filter by floor level index. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get a list') and resource ('all rooms') with specific attributes (IDs, names, positions, dimensions), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'bulc_list_levels' or 'bulc_list_walls' beyond the resource type, which prevents a perfect score.

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?

The description provides clear context for usage by stating that returned IDs are used for modify/delete operations, which helps the agent understand when to call this tool (e.g., before performing updates). It doesn't explicitly mention when not to use it or name alternatives among siblings, so it falls 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.

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