Skip to main content
Glama

batch_request

Read-only

Execute multiple ServiceNow REST API operations in one HTTP call to cut round-trips. Specify up to 50 GET, POST, PATCH, or DELETE requests with IDs, URLs, and optional bodies.

Instructions

Execute multiple ServiceNow REST API operations in a single HTTP call. Reduces round-trips by 50-70%. Each operation specifies method, URL path, and optional body. Max 50 operations per batch.

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": {
      "operations": "<operations>"
    },
    "name": "batch_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
operationsYesArray of REST operations to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. Addedv4.9.0

TDQS

C2.9/5.0
Behavior1/5

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

The description says operations can use POST/PATCH/DELETE, which are mutating actions, while annotations declare readOnlyHint=true. This is a direct contradiction. Additionally, critical batch behavior such as partial failure handling, atomicity, and response correlation is left unaddressed.

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?

The description is four sentences, front-loaded with the core action and a benefit claim. Every sentence contributes something, though the 'reduces round-trips by 50-70%' statistic is mildly promotional rather than operational.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a generic batch executor that can perform mutations, the description omits essential behavioral details: error handling, partial failure semantics, authentication expectations, and response shape. It also conflicts with its own annotations, leaving the agent unsure whether the tool is safe to call for destructive operations.

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 fully documented in the input schema. The description restates the operation structure (method, URL, body) and the 50-operation cap but adds no syntax, format, or behavioral detail beyond the schema baseline.

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?

The description states a specific verb ('Execute') and resource ('multiple ServiceNow REST API operations') with clear scope constraints (single HTTP call, max 50 operations). It is distinguishable from single-operation siblings, though it does not explicitly name alternatives like bulk_create_records or individual CRUD tools.

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?

Usage is implied through the round-trip reduction benefit and per-operation structure, but there is no explicit guidance on when to prefer this over individual tools, when not to use it, or how to handle partial failures. The agent must infer the appropriate context.

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