Skip to main content
Glama
using76
by using76

bulc_get_evac_result

Read-only

Retrieve evacuation simulation results including agent trajectories, exit statistics, and flow rate analysis for building safety assessment.

Instructions

Get detailed evacuation results including per-agent trajectories, exit statistics, and flow rate analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeTrajectoriesNoInclude full trajectory data for each agent. Default: false
includeFlowRatesNoInclude exit flow rate analysis. Default: true
includeBottlenecksNoIdentify bottleneck locations. Default: true
timeRangeNoTime range [startTime, endTime] in seconds. Default: full simulation
agentIdsNoSpecific agent IDs to include. Default: all agents

Implementation Reference

  • Handler case for the bulc_get_evac_result MCP tool. Validates input using GetEvacResultSchema and sends the 'get_evac_result' command to the BULC client for execution.
    case "bulc_get_evac_result": {
      const validated = GetEvacResultSchema.parse(args);
      result = await client.sendCommand({
        action: "get_evac_result",
        params: validated,
      });
      break;
    }
  • Zod runtime validation schema for bulc_get_evac_result tool input parameters.
    const GetEvacResultSchema = z.object({
      includeTrajectories: z.boolean().optional(),
      includeFlowRates: z.boolean().optional(),
      includeBottlenecks: z.boolean().optional(),
      timeRange: z.array(z.number()).length(2).optional(),
      agentIds: z.array(z.number().int()).optional(),
    });
  • MCP tool registration metadata for bulc_get_evac_result, including name, description, input schema, and annotations. Part of the exported evacTools array.
    {
      name: "bulc_get_evac_result",
      description:
        "Get detailed evacuation results including per-agent trajectories, " +
        "exit statistics, and flow rate analysis.",
      inputSchema: {
        type: "object" as const,
        properties: {
          includeTrajectories: {
            type: "boolean",
            description: "Include full trajectory data for each agent. Default: false",
          },
          includeFlowRates: {
            type: "boolean",
            description: "Include exit flow rate analysis. Default: true",
          },
          includeBottlenecks: {
            type: "boolean",
            description: "Identify bottleneck locations. Default: true",
          },
          timeRange: {
            type: "array",
            description: "Time range [startTime, endTime] in seconds. Default: full simulation",
            items: { type: "number" },
          },
          agentIds: {
            type: "array",
            description: "Specific agent IDs to include. Default: all agents",
            items: { type: "integer" },
          },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
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 value by specifying the types of results (trajectories, statistics, analysis), which aren't covered by annotations. However, it doesn't disclose behavioral traits like potential data size, performance implications, or prerequisites (e.g., needing 'bulc_load_evac_result' first). With annotations covering safety, this earns a baseline score for adding some context.

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 detailed evacuation results') and lists key data types without redundancy. Every word adds value, and there's no unnecessary elaboration or repetition, making it highly concise and well-structured for quick understanding.

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 complexity (retrieving detailed simulation results with 5 parameters) and the absence of an output schema, the description is moderately complete. It outlines the data types returned but doesn't specify output format, size, or how results integrate with other tools (e.g., 'bulc_load_evac_result'). With annotations covering read-only safety, it's adequate but lacks depth for full contextual understanding.

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%, with all five parameters well-documented in the input schema (e.g., defaults and purposes). The description doesn't add any parameter-specific details beyond what the schema provides, such as explaining how 'timeRange' interacts with simulation data or the impact of including trajectories. Given high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 action ('Get') and the resource ('detailed evacuation results'), specifying three types of data included: per-agent trajectories, exit statistics, and flow rate analysis. It distinguishes from siblings like 'bulc_get_evac_summary' by emphasizing 'detailed' results, though it doesn't explicitly name alternatives. This is specific but lacks direct sibling differentiation.

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 'bulc_get_evac_summary' or 'bulc_get_evac_status'. It doesn't mention prerequisites like needing a completed evacuation simulation or loaded results, nor does it specify contexts where this detailed data is preferred over summaries. This leaves the agent without clear usage cues.

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