Skip to main content
Glama
using76
by using76

bulc_list_furniture

Read-only

List all furniture items in a building design with IDs, positions, and properties to manage placement and modifications.

Instructions

Get a list of all placed furniture with their IDs, positions, and properties. Use the returned IDs for modify/delete operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoFilter by floor level index. Omit to list all.
roomNoFilter by room name or ID
categoryNoFilter by furniture category

Implementation Reference

  • The handler logic for 'bulc_list_furniture' tool: validates input schema and sends 'list_furniture' action to BULC client.
    case "bulc_list_furniture": {
      const validated = ListFurnitureSchema.parse(args);
      result = await client.sendCommand({
        action: "list_furniture",
        params: validated,
      });
      break;
  • Zod schema used for input validation of 'bulc_list_furniture' tool.
    const ListFurnitureSchema = z.object({
      level: z.number().int().optional(),
      room: z.string().optional(),
      category: z.string().optional(),
    });
  • MCP tool registration definition for 'bulc_list_furniture', including name, description, input schema, and annotations.
    {
      name: "bulc_list_furniture",
      description:
        "Get a list of all placed furniture with their IDs, positions, and properties. " +
        "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.",
          },
          room: {
            type: "string",
            description: "Filter by room name or ID",
          },
          category: {
            type: "string",
            description: "Filter by furniture category",
          },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:54-58 (registration)
    MCP server lists all tools including furnitureTools containing 'bulc_list_furniture'.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • src/index.ts:78-80 (registration)
    Dispatch routing in main tool handler: routes 'bulc_list_furniture' 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 the purpose of returned IDs (for modify/delete operations) and implies it returns all placed furniture by default, but doesn't describe pagination behavior, rate limits, or authentication requirements. With annotations covering the safety profile, a 3 is appropriate as the description adds some value but not rich behavioral context.

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. First sentence states purpose and scope, second sentence provides usage guidance. Perfectly front-loaded and appropriately sized for a list operation tool.

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 tool with good annotations and full schema coverage, the description is mostly complete. It explains what the tool returns and how to use the results. The main gap is lack of output schema, so the description doesn't detail the return format structure, but this is partially mitigated by mentioning specific return attributes (IDs, positions, properties).

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%, so the schema already documents all three parameters with clear descriptions. The description doesn't add any parameter-specific information beyond what's in the schema, but it implies filtering capability through 'Get a list of all placed furniture' with the schema providing the filter details. Baseline 3 is correct when schema does the heavy lifting.

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 verb 'Get' and resource 'list of all placed furniture' with specific attributes (IDs, positions, properties). It distinguishes from siblings like bulc_list_furniture_catalog (which likely lists catalog items rather than placed instances) and bulc_place_furniture/modify_furniture/delete_furniture (which are mutation operations rather than read operations).

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 ('Use the returned IDs for modify/delete operations'), which implicitly guides when to use this tool versus mutation tools. However, it doesn't explicitly state when NOT to use it or name specific alternatives for different filtering needs, though the schema parameters suggest filtering capabilities.

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