BCD — Bridge Control Delegate

edit_docx

Replace exact text in a Word .docx even where it spans formatting runs, writing a new outputPath (the original is kept). oldText must occur expectedOccurrences times (default 1). part: body (default), header, footer or all. mode xml replaces XML copied from read_file docxMode xml. Images, fields and untouched parts are preserved; signed files are refused.

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>",
      "oldText": "<oldText>",
      "newText": "<newText>"
    },
    "name": "edit_docx"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No		text
`part`	No
`newText`	Yes
`oldText`	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.
`expectedOccurrences`	No
`includeHeadersFooters`	No

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.3/5.0

Behavior5/5

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

Annotations declare non-destructive (destructiveHint=false, readOnlyHint=false), and the description adds rich context beyond them: the original is kept because a new outputPath is written, images/fields/untouched parts are preserved, and signed files are refused. This is exactly the extra behavioral disclosure annotations cannot supply.

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?

Dense and front-loaded: the core action leads, then output behavior, occurrence rule, part/mode options, and preservation/refusal caveats follow. Slightly run-on but every clause carries information.

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?

With 10 parameters, low schema coverage and no output schema, the description covers the essential behavior, defaults and edge cases (signed-file refusal, preservation) but never states what the call returns. That omission is the main remaining gap.

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 only 20%, so the description must compensate. It explains oldText occurrence semantics, the part values (body default, header, footer, all) and mode xml, but leaves newText, inputPath and includeHeadersFooters undocumented in both schema and description, so compensation is partial.

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?

States a specific verb and resource ('Replace exact text in a Word .docx') and adds the distinguishing scope detail 'even where it spans formatting runs', which separates it from generic write_file/edit_block siblings. An agent can identify the operation without opening the schema.

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?

Provides concrete when-to-use conditions: mode xml requires XML copied from read_file with docxMode xml, and oldText must occur expectedOccurrences times. It gives clear context but does not explicitly rule out alternatives or state when-not to use it.

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?