Skip to main content
Glama

ncp_batch

Read-only

Run multiple read-only ncp_call requests concurrently and return results in input order, with per-item failure reporting that lets remaining calls complete.

Instructions

Run several read-only ncp_call requests concurrently; results keep the input order.

Each item takes the ncp_call keys: service, action, and optionally params, fields, profile, paginate. A per-item 'profile' overrides the batch profile. Failures are reported per item and do not stop the others.

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": {
      "calls": "<calls>"
    },
    "name": "ncp_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYes
profileNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: results preserve input order and per-item failures are isolated rather than aborting the batch. It stops short of noting concurrency limits, request volume, or rate-limit implications for an open-world batch.

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 purpose, then item structure, then override and failure semantics in a tight few lines with no filler. Slight terseness on the item key list, but every sentence 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?

An output schema exists, so return values need not be explained, and the description covers the remaining essentials: item shape, ordering, error isolation, and profile precedence. Complete enough to invoke correctly; missing only per-item required/optional distinctions and any concurrency or volume caveats.

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% and the 'calls' array items are open (additionalProperties: true with no documented keys), so the description is the only source of item structure. It does enumerate the accepted keys (service, action, params, fields, profile, paginate) and explain that per-item profile overrides the batch profile, which is substantial compensation. It still omits which keys are required per item and the types/format of those values, leaving gaps the schema cannot fill.

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?

Uses a specific verb and resource ('Run several read-only ncp_call requests concurrently') and immediately distinguishes this tool from the single-call sibling ncp_call. The scoping word 'read-only' and the ordering guarantee make the purpose unambiguous.

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 makes clear this is the tool for fanning out multiple ncp_call requests in parallel, which implicitly positions ncp_call as the single-request alternative. It does not explicitly say 'use ncp_call instead when you have one call' or warn against expensive/conflicting batches, so no exclusion guidance is present.

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

Deploy Server

Other Tools