Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

getRpaTaskDetail

Retrieves detailed information for a specific RPA task using its task ID in the DICloak Local API, helping you inspect task status and results.

Instructions

Get RPA task details

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": {
      "taskId": "<taskId>"
    },
    "name": "getRpaTaskDetail"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, what happens when taskId does not exist, whether results are cached or eventually consistent, or what the response shape looks like. For a tool with zero annotation coverage this is a complete gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single short sentence is front-loaded and free of filler, so there is no wasted wording. However, its brevity comes from under-specification rather than efficient communication, so it earns only a middling score.

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

Completeness1/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 0% parameter coverage, the description is the only source of information and it says essentially nothing about inputs, outputs, or failure modes. An agent cannot call this tool correctly from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter taskId, so the description must compensate and does not. It never states whether taskId is a numeric ID, a UUID, or the identifier returned by another tool, leaving the only required input unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get RPA task details" only restates the tool name getRpaTaskDetail: a generic verb plus the same noun. It never says what a "task detail" record contains or how it differs from the sibling query-rpa-batch-results, so an agent gets no real disambiguation.

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 when-to-use guidance, no prerequisite (e.g., needing a task started elsewhere), and no mention of alternatives such as query-rpa-batch-results. Only the word "details" hints that this is a single-record lookup, which is inference rather than stated guidance.

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