BCD — Bridge Control Delegate

edit_spreadsheet

Edit cells or ranges, or append rows, in an Excel workbook (xlsx, xlsm, xls) into a new outputPath, keeping the original. Keeps styles, charts, images, merged cells, tables and VBA (never run); formulas recalculate where supported. Use it when edit_block refuses an in-place edit. Reports what was preserved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>",
      "edits": "<edits>"
    },
    "name": "edit_spreadsheet"
  }
}

Input Schema

Name	Required	Description
`edits`	Yes
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`inputPath`	Yes
`outputPath`	Yes
`workSessionId`	No	Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / workSessionId

Added value: +{
+  "description": "Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.",
+  "format": "uuid",
+  "type": "string"
+}

First observedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds significant behavioral context: it writes to a new outputPath, keeps the original, preserves styles/charts/images/merged cells/tables/VBA (never run), recalculates formulas, and reports what was preserved. This goes well beyond the annotations and is exactly what an agent needs for a mutation tool.

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, dense, front-loaded sentence plus one short follow-up. Every phrase adds value: file types, edit types, output behavior, preservation guarantees, formula handling, and sibling routing. No waste.

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 mutation tool with annotations and a complex nested schema, the description covers the key behaviors: output file creation, preservation of features, formula recalculation, VBA safety, and report. It does not describe the edits structure (cell/range/rows/values/sheetName/sheetIndex), which is a gap given 40% schema coverage, but the essential behavioral context is present.

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 coverage is 40% (only deviceId and workSessionId have descriptions; inputPath, outputPath, edits lack descriptions). The description mentions inputPath/outputPath implicitly via 'into a new outputPath' and 'keeping the original', but does not describe the edits schema at all. Since schema coverage is low, the description should compensate more, but it does convey the core semantics of input/output paths.

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 specific verb+resource: 'Edit cells or ranges, or append rows, in an Excel workbook (xlsx, xlsm, xls) into a new outputPath'. It also references the sibling 'edit_block' and distinguishes the two by when to use each. This is a clear, actionable purpose statement.

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?

Explicit guidance: 'Use it when edit_block refuses an in-place edit.' This directly tells the agent the condition under which to choose this tool over the alternative, with no ambiguity.

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

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?