BCD — Bridge Control Delegate

read_multiple_files

Read-only

Read up to 20 files in one call, each under its own path header with its own error if it fails. Same formats as read_file; offset/length apply to every file.

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": {
      "paths": "<paths>"
    },
    "name": "read_multiple_files"
  }
}

Input Schema

Name	Required	Description
`paths`	Yes
`length`	No
`offset`	No
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`maxBytes`	No
`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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: per-file error isolation ('its own error if it fails') and that offset/length apply uniformly to every file. It does not cover maxBytes defaults or truncation behavior.

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?

Two dense sentences, front-loaded with the scope and cap, then the error-isolation and format/param semantics. No filler.

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 no output schema, the description usefully sketches the return shape (per-path headers, per-file errors). For a 6-parameter tool it still leaves maxBytes semantics and the handling of partial failures ambiguous, but the essentials for correct invocation are 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 description coverage is only 33%: deviceId and workSessionId are documented inline, but offset, length, and maxBytes are not. The description usefully clarifies that offset/length apply to every file, which the schema does not convey, but maxBytes remains undocumented in both places.

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?

Clear verb (Read) plus resource (multiple files) with explicit scope: up to 20 files, each under its own path header. It references read_file for format compatibility, which hints at the sibling relationship, but it never states the routing rule for choosing one over the other.

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?

Batch usage is implied by 'in one call' and the 20-file cap, but there is no explicit when-to-use / when-not-to-use guidance and no mention of when to prefer plain read_file or a search tool instead. An agent must infer the routing.

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?