Skip to main content
Glama
using76
by using76

bulc_get_home_info

Read-only

Retrieve project details like file status, room counts, and structural elements from BULC Building Designer to analyze building design data.

Instructions

Get general information about the current project including file path, modification status, level count, room count, wall count, and furniture count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The specific handler case for the 'bulc_get_home_info' tool. It sends a 'get_home_info' command to the BULC client with empty parameters and processes the result.
    case "bulc_get_home_info": {
      result = await client.sendCommand({
        action: "get_home_info",
        params: {},
      });
      break;
    }
  • Tool definition including name, description, input schema (empty object since no parameters), and annotations indicating it's read-only.
    {
      name: "bulc_get_home_info",
      description:
        "Get general information about the current project including file path, modification status, level count, room count, wall count, and furniture count.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • src/index.ts:152-162 (registration)
    Routing logic in the main CallToolRequest handler that directs 'bulc_get_home_info' calls to the context tool handler.
      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);
    }
  • src/index.ts:54-58 (registration)
    Registers the list of all tools (including 'bulc_get_home_info' via contextTools spread into allTools) for the ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
Behavior4/5

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

Annotations indicate read-only and non-destructive behavior, which the description aligns with by using 'Get'. The description adds value by specifying the types of information returned (e.g., counts, status), which annotations do not cover. However, it lacks details on potential errors or performance characteristics.

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 core purpose ('Get general information about the current project') and lists specific data points without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function.

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 zero-parameter read-only tool with annotations covering safety, the description provides sufficient context by detailing the information returned. However, without an output schema, it could benefit from clarifying the format of the returned data (e.g., structured object vs. plain text).

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 tool has zero parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter details, earning a high baseline score for this context.

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 the resource 'general information about the current project', specifying concrete data points like file path, modification status, and various counts. It distinguishes itself from siblings like 'bulc_get_evac_settings' or 'bulc_get_fds_data' by focusing on overall project metadata rather than specific subsystems.

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 implies usage for retrieving project overview information but does not explicitly state when to use this tool versus alternatives like 'bulc_get_spatial_context' or other 'get_' siblings. No exclusions or prerequisites are mentioned, leaving usage context inferred rather than clearly defined.

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