Skip to main content
Glama
using76
by using76

bulc_redo

Destructive

Restore the last undone action in BULC Building Designer to continue building design work, showing what changes were reapplied.

Instructions

Redo the last undone operation. Returns information about what was redone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'bulc_redo' tool, which sends a 'redo' command to the BULC client with empty parameters.
    case "bulc_redo": {
      result = await client.sendCommand({
        action: "redo",
        params: {},
      });
      break;
    }
  • Registration of the 'bulc_redo' tool in the contextTools array, including name, description, empty input schema, and annotations.
    {
      name: "bulc_redo",
      description: "Redo the last undone operation. Returns information about what was redone.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: true,
      },
    },
  • src/index.ts:150-162 (registration)
    Routing logic in main server handler that dispatches 'bulc_redo' (and other context tools) to handleContextTool.
    // Context tools (get_spatial_context, get_home_info, levels, undo, redo, save)
    if (
      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:40-41 (registration)
    Inclusion of contextTools (which contains 'bulc_redo') into the full list of available tools served to MCP clients.
    const allTools = [
      ...contextTools,      // 8 tools: spatial context, home info, levels, undo/redo, save
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description doesn't contradict. The description adds valuable behavioral context by specifying that it 'Returns information about what was redone', which isn't covered by annotations. However, it doesn't mention potential side effects or limitations beyond the basic operation.

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 serve a distinct purpose: the first states the action, the second describes the return value. No wasted words or unnecessary elaboration.

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 tool with clear annotations, the description provides sufficient context about what the tool does and what it returns. The only minor gap is the lack of output schema, but the description compensates by stating what information is returned.

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?

With 0 parameters and 100% schema coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, which is correct for this tool.

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 'Redo' and specifies 'the last undone operation', which distinguishes it from sibling tools like 'bulc_undo'. It's specific about what it does and differentiates from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly indicates when to use this tool: 'Redo the last undone operation'. This provides clear context for its application relative to the 'bulc_undo' tool, establishing a direct usage relationship.

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