Skip to main content
Glama

bx_workbench_open

Read-onlyIdempotent

Return the independent workbench URL for host-controlled opening, with an optional project link; this does not start analysis.

Instructions

返回独立工作台当前地址,由宿主打开,不启动分析。 / Return the independent B-335 workbench URL. Optional project link; browser opening is controlled by the host. Does not start analysis.

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": "bx_workbench_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNo

Output Schema

NameRequiredDescriptionDefault
dataYes
kindYes
productYes
api_versionYes
business_decisionYes
execution_authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-rc.9-linux.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds real behavioral context beyond them: it only resolves a URL, does not launch analysis, and the actual browser opening is the host's responsibility — a caller-relevant distinction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core outcome, followed by the scope caveats. The bilingual duplication is standard practice and each sentence carries information, though the two halves are near-verbatim rather than complementary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single-parameter, side-effect-free URL resolver with an output schema and strong annotations. The description covers the only ambiguities an agent could have — does this run analysis, and does it open a browser — so nothing material is missing.

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 definition must compensate. 'Optional project link' gives the lone project_id parameter meaning (it associates the workbench with a project) beyond the bare UUID pattern, but does not explain behavior when omitted or whether an invalid/missing project changes the returned URL.

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?

Names a specific resource and action: returns the current URL of the independent B-335 workbench. The 'does not start analysis' clause implicitly distinguishes it from analysis-starting siblings, though it never names them directly.

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

Usage Guidelines3/5

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

'Optional project link' and 'browser opening is controlled by the host' imply when the tool is appropriate (fetch a URL for the host to open), but there is no explicit when-to-use/when-not guidance or named alternative for getting analysis results or workbench state.

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