iSuite Operations MCP Server

get_batch_history

Retrieve the complete execution history for a batch job definition, including optional throughput and timing metrics.

Instructions

Get the complete execution history for a batch job definition.

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": {
      "batchDefinitionId": "<batchDefinitionId>"
    },
    "name": "get_batch_history"
  }
}

Input Schema

Name	Required	Description
`batchDefinitionId`	Yes	The batch definition ID (not execution ID) to retrieve history for.
`limit`	No	Number of past executions to return (default 20).
`includeMetrics`	No	Include throughput/timing metrics for each run (default false).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It correctly implies a read operation (get) but does not detail what 'complete execution history' means (e.g., fields returned, pagination, or any side effects). Adequate but lacks depth.

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 a single concise sentence, easy to parse. However, it could include slightly more detail without becoming verbose, so not a perfect 5.

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?

Given the tool has three well-documented parameters and no output schema, the description is minimally sufficient. It lacks context about the output format, typical use cases, or any limitations, leaving gaps for a complex tool.

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 each parameter already has a description. The tool description adds no new semantic meaning beyond restating the resource; baseline 3 is appropriate.

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 clearly states the tool retrieves the complete execution history for a batch job definition, which distinguishes it from siblings like get_batch_status (current status) and get_job_history (individual job history). However, it does not elaborate on what the history includes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus other history or status tools, such as get_batch_status for current state or get_schedule_history for scheduled runs. The agent must infer from context alone.

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