Skip to main content
Glama
using76
by using76

bulc_get_fds_data

Read-only

Retrieve fire safety configuration data for building furniture items, including fire sources, detectors, sprinklers, HVAC systems, and thermocouples to support fire simulation analysis.

Instructions

Get FDS configuration for a furniture item. Returns the FDS category (fire source, detector, sprinkler, HVAC, thermocouple) and its configuration parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
furnitureIdYesFurniture ID to get FDS data from (from bulc_list_furniture)

Implementation Reference

  • Executes the bulc_get_fds_data tool by validating input with Zod schema and sending a 'get_fds_data' command to the BULC client.
    case "bulc_get_fds_data": {
      const validated = GetFdsDataSchema.parse(args);
      result = await client.sendCommand({
        action: "get_fds_data",
        params: validated,
      });
      break;
    }
  • Tool schema definition including name, description, input schema for furnitureId, and annotations indicating read-only operation.
    {
      name: "bulc_get_fds_data",
      description:
        "Get FDS configuration for a furniture item. " +
        "Returns the FDS category (fire source, detector, sprinkler, HVAC, thermocouple) " +
        "and its configuration parameters.",
      inputSchema: {
        type: "object" as const,
        properties: {
          furnitureId: {
            type: "string",
            description: "Furniture ID to get FDS data from (from bulc_list_furniture)",
          },
        },
        required: ["furnitureId"],
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • Zod validation schema for bulc_get_fds_data input parameters.
    const GetFdsDataSchema = z.object({
      furnitureId: z.string(),
    });
  • src/index.ts:84-94 (registration)
    Registers routing of bulc_get_fds_data calls to the handleFdsDataTool function in the MCP server's tool call handler.
    if (
      name === "bulc_get_fds_data" ||
      name === "bulc_set_fds_fire_source" ||
      name === "bulc_set_fds_detector" ||
      name === "bulc_set_fds_sprinkler" ||
      name === "bulc_set_fds_hvac" ||
      name === "bulc_set_fds_thermocouple" ||
      name === "bulc_clear_fds_data"
    ) {
      return await handleFdsDataTool(name, safeArgs);
    }
  • src/index.ts:45-45 (registration)
    Includes fdsDataTools (containing bulc_get_fds_data schema) in the allTools array served via ListToolsRequest.
    ...fdsDataTools,      // 7 tools: get, fire_source, detector, sprinkler, hvac, thermocouple, clear
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 what data is returned (FDS categories and configuration parameters), which goes beyond the annotations. However, it doesn't describe behavioral aspects like error conditions, performance characteristics, or data format details.

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 perfectly concise - two sentences that efficiently convey the tool's purpose and return values without any wasted words. It's front-loaded with the core functionality and follows with output details, making it easy for an agent to parse quickly.

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 tool with good annotations and complete parameter documentation, the description provides adequate context about what data is retrieved. However, without an output schema, the description should ideally provide more detail about the return format (structure, data types, example values) to help the agent understand how to process the response.

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 fully documents the single required parameter (furnitureId). The description adds no additional parameter semantics beyond what's in the schema, but doesn't need to since schema coverage is complete. The baseline score of 3 reflects adequate parameter documentation through the schema alone.

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 tool's purpose: 'Get FDS configuration for a furniture item' with specific output details (FDS categories and configuration parameters). It distinguishes from siblings like bulc_clear_fds_data (deletion) and bulc_set_fds_* tools (configuration), but doesn't explicitly name alternatives for similar retrieval operations.

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?

The description provides no guidance on when to use this tool versus alternatives. While it implies usage for retrieving FDS configuration, it doesn't mention when to choose this over other data retrieval tools like bulc_get_point_data or bulc_get_fds_status, nor does it specify prerequisites or contextual constraints.

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