Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

query-rpa-batch-results

Fetch RPA batch results using a batch ID to review automation outcomes and execution status.

Instructions

Query RPA batch results by batch ID

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": {
      "batchId": "<batchId>"
    },
    "name": "query-rpa-batch-results"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Query' suggests a read operation, but the description says nothing about permissions, whether an incomplete or still-running batch returns partial results, pagination, or result ordering. For a batch-results tool where incomplete processing is a realistic state, these omissions matter.

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 definition is a single short clause with the resource and the key front-loaded and zero filler. Its brevity, however, reflects under-specification rather than disciplined trimming.

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?

With no output schema, no annotations, and an undocumented parameter, the description should explain the shape of the returned results and how a batch ID is obtained. It supplies neither, so an agent can identify the tool but cannot confidently predict or interpret its output.

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%, so the schema documents only that batchId is a required string. The description partially compensates by establishing that the parameter is the batch identifier used as the lookup key, but it gives no format, source (where to obtain a batch ID), or example value.

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 gives a specific verb and resource ('Query RPA batch results') plus the lookup key ('by batch ID'), so an agent knows exactly what the tool retrieves. It does not distinguish itself from plausible siblings such as getRpaTaskDetail, leaving the batch-vs-task boundary implicit.

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?

There is no statement of when to use this tool, when not to, or what alternative to pick for a single RPA task versus an entire batch. The only implied usage comes from the phrase 'by batch ID', so the agent must infer the selection criteria from the name alone.

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