Skip to main content
Glama
using76
by using76

bulc_list_levels

Read-only

Retrieve all floor levels including names, elevations from ground, and ceiling heights for building design projects.

Instructions

Get all floor levels with their names, elevations (height from ground), and floor heights (ceiling height).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for 'bulc_list_levels' tool: sends the 'list_levels' command to the BULC client with empty params.
    case "bulc_list_levels": {
      result = await client.sendCommand({
        action: "list_levels",
        params: {},
      });
      break;
    }
  • Tool schema/definition for 'bulc_list_levels': defines name, description, empty input schema, and read-only annotation.
    {
      name: "bulc_list_levels",
      description:
        "Get all floor levels with their names, elevations (height from ground), and floor heights (ceiling height).",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:152-162 (registration)
    Registration/routing for context tools including 'bulc_list_levels': routes tool calls matching the name to handleContextTool.
      name === "bulc_get_spatial_context" ||
      name === "bulc_get_home_info" ||
      name === "bulc_list_levels" ||
      name === "bulc_create_level" ||
      name === "bulc_set_current_level" ||
      name === "bulc_undo" ||
      name === "bulc_redo" ||
      name === "bulc_save"
    ) {
      return await handleContextTool(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, indicating a safe read operation. The description adds value by specifying the data returned (names, elevations, floor heights), but doesn't cover behavioral aspects like response format, pagination, 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 a single, efficient sentence that front-loads the purpose and key details without any wasted words. It's appropriately sized for a simple list tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no parameters and no output schema, the description is adequate but minimal. It specifies what data is returned, but lacks context on format, ordering, or completeness, which could be helpful given 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score for not adding unnecessary information.

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') and resource ('all floor levels') with specific attributes (names, elevations, floor heights). It distinguishes from many siblings (e.g., bulc_list_rooms, bulc_list_walls) by specifying floor levels, though it doesn't explicitly differentiate from all list tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or compare with other list tools like bulc_list_rooms or bulc_list_walls, leaving the agent to infer usage.

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