Skip to main content
Glama
using76
by using76

bulc_set_evac_time

Destructive

Configure evacuation simulation duration and time step resolution to model building evacuation scenarios accurately.

Instructions

Set evacuation simulation time parameters. Controls total simulation duration and time step resolution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
simulationTimeYesTotal simulation time in seconds. Default: 300
timeStepNoSimulation time step in seconds. Default: 0.1

Implementation Reference

  • Registration of the 'bulc_set_evac_time' tool in the evacTools array, including name, description, input schema, and annotations.
    {
      name: "bulc_set_evac_time",
      description:
        "Set evacuation simulation time parameters. " +
        "Controls total simulation duration and time step resolution.",
      inputSchema: {
        type: "object" as const,
        properties: {
          simulationTime: {
            type: "number",
            description: "Total simulation time in seconds. Default: 300",
          },
          timeStep: {
            type: "number",
            description: "Simulation time step in seconds. Default: 0.1",
          },
        },
        required: ["simulationTime"],
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • Zod schema used for input validation in the handler for bulc_set_evac_time.
    const SetEvacTimeSchema = z.object({
      simulationTime: z.number().positive(),
      timeStep: z.number().positive().optional(),
    });
  • Handler logic within handleEvacTool function: validates input using SetEvacTimeSchema and sends 'set_evac_time' command to BULC client.
    case "bulc_set_evac_time": {
      const validated = SetEvacTimeSchema.parse(args);
      result = await client.sendCommand({
        action: "set_evac_time",
        params: validated,
      });
      break;
    }
  • src/index.ts:54-58 (registration)
    MCP server registration of all tools including evacTools (which contains bulc_set_evac_time) via ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: allTools,
      };
    });
  • src/index.ts:135-137 (registration)
    Routing logic in main CallToolRequestHandler that directs bulc_set_evac_time calls to handleEvacTool.
    if (name.startsWith("bulc_") && name.includes("evac")) {
      return await handleEvacTool(name, safeArgs);
    }
Behavior3/5

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

Annotations already indicate this is a destructive write operation (readOnlyHint: false, destructiveHint: true). The description adds useful context about what gets modified ('evacuation simulation time parameters'), but doesn't provide additional behavioral details like whether changes are reversible, if there are validation constraints, or what happens to ongoing simulations. No contradiction with annotations exists.

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 with two sentences that each earn their place. The first sentence establishes the core purpose, and the second clarifies the scope of control. There's zero wasted language or redundancy.

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 destructive mutation tool with no output schema, the description adequately covers the basic purpose but lacks important contextual information. It doesn't explain what happens after setting these parameters, whether validation occurs, or how this interacts with other evacuation tools. Given the complexity implied by the sibling tools list, more completeness would be helpful.

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 already fully documents both parameters with clear descriptions and defaults. The description adds marginal value by confirming these parameters control 'total simulation duration and time step resolution,' but doesn't provide additional semantic context beyond what's in the schema.

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 specific action ('Set'), the target resource ('evacuation simulation time parameters'), and the scope of control ('total simulation duration and time step resolution'). It distinguishes itself from sibling tools like 'bulc_set_simulation_time' by focusing specifically on evacuation simulation timing rather than general simulation time settings.

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 like 'bulc_set_simulation_time' or 'bulc_set_evac_model', nor does it mention prerequisites such as needing an existing evacuation simulation setup. It simply states what the tool does without contextual usage information.

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