nx-ai-bridge

Overview Schema Source Related Servers Discussions Admin

nx_batch

Runs multiple tool calls in sequence as one unit, starting the NX window once to reduce overhead and returning one result per command.

Instructions

Run several tool calls in order as one unit. In batch mode (no NX window) this starts NX only once, which is much faster than separate calls. Returns one result per command.

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": {
      "commands": "<commands>"
    },
    "name": "nx_batch"
  }
}

Input Schema

Name	Required	Description	Default
`commands`	Yes	List of {"tool": name, "params": {...}} objects.
`stop_on_error`	No	Stop at the first failing command.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses ordering ("in order"), the one-result-per-command contract, and the NX-startup optimization, but says nothing about mutation safety, failure behavior when stop_on_error is false (partial vs. aborted results), or whether the batch is atomic.

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?

Three short sentences, each carrying distinct information: what it does, why it is faster, and what it returns. Nothing is redundant and the core purpose is front-loaded.

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?

For a meta-tool that executes arbitrary sibling commands with no output schema and no annotations, the definition covers ordering and result count but leaves the return shape and failure semantics vague. An agent still has to guess how per-command results and errors are keyed.

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 100%, so both parameters are already documented in the schema. The description adds only the mapping of commands to results ("one result per command") and does not expand on the {"tool", "params"} shape or what command names are valid. Baseline 3 applies.

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?

"Run several tool calls in order as one unit" gives a specific verb and resource plus the key semantic (sequential execution as one unit). It implicitly distinguishes itself from making separate sibling calls, but it never states which tools can be batched or any restrictions on nesting.

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 clear motivation for using this tool over the alternative: "this starts NX only once, which is much faster than separate calls." It lacks explicit when-not guidance, such as whether it is safe to batch destructive operations or when a single call is preferable.

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