Skip to main content
Glama
using76
by using76

bulc_list_walls

Read-only

Retrieve wall data including IDs, coordinates, thickness, and height from building designs to identify and manage structural elements for modification or removal.

Instructions

Get a list of all walls with their IDs, coordinates, thickness, and height. Use the returned IDs for modify/delete operations.

Input Schema

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

Implementation Reference

  • Handler logic for 'bulc_list_walls': validates input using ListWallsSchema and sends 'list_walls' command to BULC client via getBulcClient().
    case "bulc_list_walls": {
      const validated = ListWallsSchema.parse(args);
      result = await client.sendCommand({
        action: "list_walls",
        params: validated,
      });
      break;
    }
  • Zod validation schema for bulc_list_walls input (optional level filter).
    const ListWallsSchema = z.object({
      level: z.number().int().optional(),
    });
  • Tool definition/registration in wallTools array, including name, description, inputSchema, and annotations.
    {
      name: "bulc_list_walls",
      description:
        "Get a list of all walls with their IDs, coordinates, thickness, and height. " +
        "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.",
          },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:73-76 (registration)
    MCP server request handler routes 'bulc_*wall*' tools (including bulc_list_walls) to handleWallTool.
    // Wall tools
    if (name.startsWith("bulc_") && name.includes("wall")) {
      return await handleWallTool(name, safeArgs);
    }
  • src/index.ts:54-58 (registration)
    Registers allTools (including wallTools with bulc_list_walls) for ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
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 value by specifying the returned data fields (IDs, coordinates, thickness, height) and the purpose of IDs for subsequent operations, but it does not 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 front-loaded with the core purpose in the first sentence and adds a practical usage note in the second sentence. Both sentences are essential, with zero waste or redundancy, making it efficiently structured and appropriately sized for the tool's complexity.

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 low complexity (one optional parameter, no output schema), the description is complete enough for a read-only list operation. It covers purpose, usage, and return data, but lacks details on output format (e.g., structure of the list) or error handling, which could be beneficial despite the absence of an output schema.

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?

The input schema has 100% description coverage, with the 'level' parameter fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as default behavior when 'level' is omitted. Since schema coverage is high, the baseline score of 3 is appropriate.

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 a list') and resource ('all walls') with specific attributes (IDs, coordinates, thickness, height). It distinguishes from siblings like 'bulc_create_wall' (create) and 'bulc_modify_wall' (modify) by focusing on listing, and explicitly mentions using IDs for modify/delete operations, which helps differentiate it from other list tools like 'bulc_list_rooms'.

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 'Use the returned IDs for modify/delete operations,' which implies this tool should be used to retrieve IDs before performing modifications or deletions. However, it does not explicitly mention when not to use it or name specific alternatives, such as filtering by level vs. listing all.

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