Skip to main content
Glama
using76
by using76

bulc_list_furniture_catalog

Read-only

Browse and filter furniture items from the BULC catalog to find specific pieces for building design projects, returning IDs needed for placement.

Instructions

Get a list of available furniture items from the catalog. Use category filter to narrow down results. Returns catalog IDs needed for bulc_place_furniture.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (e.g., 'Seats', 'Tables', 'Beds', 'Doors', 'Windows', 'Lights')
searchNoSearch by name (partial match)
limitNoMaximum number of results to return. Default: 20

Implementation Reference

  • Core handler logic: validates input using ListCatalogSchema and sends 'list_furniture_catalog' action to BULC client.
    case "bulc_list_furniture_catalog": {
      const validated = ListCatalogSchema.parse(args);
      result = await client.sendCommand({
        action: "list_furniture_catalog",
        params: validated,
      });
      break;
    }
  • Zod validation schema for tool parameters: category (optional string), search (optional string), limit (optional positive integer).
    const ListCatalogSchema = z.object({
      category: z.string().optional(),
      search: z.string().optional(),
      limit: z.number().int().positive().optional(),
    });
  • Tool metadata registration including name, description, input schema, and annotations (read-only, non-destructive).
    {
      name: "bulc_list_furniture_catalog",
      description:
        "Get a list of available furniture items from the catalog. " +
        "Use category filter to narrow down results. " +
        "Returns catalog IDs needed for bulc_place_furniture.",
      inputSchema: {
        type: "object" as const,
        properties: {
          category: {
            type: "string",
            description:
              "Filter by category (e.g., 'Seats', 'Tables', 'Beds', 'Doors', 'Windows', 'Lights')",
          },
          search: {
            type: "string",
            description: "Search by name (partial match)",
          },
          limit: {
            type: "integer",
            description: "Maximum number of results to return. Default: 20",
          },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:40-51 (registration)
    Global tool registry: includes furnitureTools in the complete list of MCP tools served via listTools.
    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
    ];
  • Main MCP callTool dispatcher routes furniture tools (including bulc_list_furniture_catalog) to handleFurnitureTool.
    // Furniture tools
    if (name.startsWith("bulc_") && name.includes("furniture")) {
      return await handleFurnitureTool(name, safeArgs);
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 returning catalog IDs needed for placement, which isn't covered by annotations. However, it doesn't disclose behavioral traits like pagination, rate limits, or error conditions beyond what annotations provide.

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 extremely concise with just two sentences that both earn their place: the first states the core purpose, the second provides filtering guidance and downstream usage context. No wasted words, perfectly front-loaded with essential information.

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 read-only list operation with full parameter documentation and clear annotations, the description provides adequate context. The mention of catalog IDs for placement adds valuable downstream usage information. The main gap is the lack of output schema, but the description compensates somewhat by indicating what the return values are used for.

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 input schema already fully documents all three parameters (category, search, limit) with clear descriptions and defaults. The description mentions the category filter but adds no additional semantic information beyond what's in the schema, meeting the baseline 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 verb ('Get a list') and resource ('available furniture items from the catalog'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this from sibling tools like 'bulc_list_furniture' or 'bulc_place_furniture' beyond mentioning the latter in the return value context.

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 provides implied usage guidance by mentioning the category filter and referencing 'bulc_place_furniture' as a downstream tool, but it doesn't explicitly state when to use this versus alternatives like 'bulc_list_furniture' or other catalog-related tools. No explicit when-not-to-use or prerequisite information is provided.

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