Skip to main content
Glama
using76
by using76

bulc_list_evac_exits

Read-only

Identify and list all evacuation exits in building designs by detecting doors converted to exits, with optional floor-level filtering for targeted analysis.

Instructions

List all detected evacuation exits (doors converted to exits).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoFilter by floor level

Implementation Reference

  • Handler case for the 'bulc_list_evac_exits' tool. Validates input arguments using ListEvacExitsSchema and forwards the 'list_evac_exits' action to the BULC client.
    case "bulc_list_evac_exits": {
      const validated = ListEvacExitsSchema.parse(args);
      result = await client.sendCommand({
        action: "list_evac_exits",
        params: validated,
      });
      break;
  • Tool registration/definition for 'bulc_list_evac_exits' in the evacTools array, including name, description, input schema, and annotations.
    {
      name: "bulc_list_evac_exits",
      description:
        "List all detected evacuation exits (doors converted to exits).",
      inputSchema: {
        type: "object" as const,
        properties: {
          level: {
            type: "integer",
            description: "Filter by floor level",
          },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
  • Zod schema used for input validation of the 'bulc_list_evac_exits' tool.
    const ListEvacExitsSchema = z.object({
      level: z.number().int().optional(),
    });
Behavior3/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds minimal behavioral context by specifying 'detected' evacuation exits, which implies a retrieval of pre-existing data, but does not disclose details like pagination, rate limits, or error conditions. With annotations covering safety, the description adds some value but lacks rich behavioral disclosure.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It is front-loaded with the main action and resource, making it easy to parse and understand quickly, with zero wasted information.

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?

Given the tool's simplicity (one optional parameter, read-only operation, no output schema), the description is adequate but minimal. It covers the basic purpose but lacks details on output format, error handling, or integration with other tools, which could be helpful for an agent in a complex server environment with many siblings.

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% for the single parameter 'level', which is documented as 'Filter by floor level'. The description does not add any meaning beyond this, such as format constraints or default behavior. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 ('List') and resource ('evacuation exits') with the clarifying detail 'doors converted to exits', making the purpose specific. However, it does not explicitly differentiate from sibling tools like 'bulc_list_evac_agents' or 'bulc_list_evac_stairs', which also list evacuation-related items, so it lacks sibling differentiation for a perfect score.

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, such as other list tools for evacuation components or filtering options. It mentions 'detected' evacuation exits but does not specify prerequisites, exclusions, or contextual usage, leaving the agent without clear direction.

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