Skip to main content
Glama
Sign In
bonsai-mcp

bonsai-mcp

by nhantruong96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bl_isolate

Hide all IFC elements except the specified GlobalIds and return the viewport image. Set restore=true to show everything again.

Instructions

Hide everything except the given GlobalIds and return the image.

Pass restore=true to unhide everything again. Hiding is viewport-only; no IFC data is touched.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bl_isolate"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidsNo
widthNo
restoreNo
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It transparently discloses that hiding is viewport-only, does not touch IFC data, and can be reversed with restore=true. It does not cover edge cases like null guids or persistent state across calls, but the most important safety and reversibility traits are explicit.

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 three compact sentences with no filler. The core behavior is front-loaded, followed by the restore mechanism and the non-destructive guarantee.

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?

The description covers the main operation and reversible behavior, but with no output schema and no annotations, it leaves some context implicit. An agent still has to infer the meaning of width and timeout, how the returned image is represented, and what happens when guids is null.

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 0%, so the description must compensate for all four parameters. It clarifies that guids are the GlobalIds to keep visible and that restore=true unhides everything, but it adds no meaning for width or timeout. This is partial compensation for the schema gap.

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 states a clear action: hide everything except the specified GlobalIds and return the image. This distinguishes it from siblings like bl_screenshot or bl_focus_element by describing the isolation behavior and its output.

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

Usage Guidelines4/5

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

The description gives a practical usage context: use this to isolate certain elements and produce an image, and pass restore=true to undo the hiding. It does not explicitly name when not to use it or mention alternatives, but the context is clear and no exclusions are needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools