Skip to main content
Glama
Sign In
AgentRPA

AgentRPA

by c8xm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rpa_query_job

Retrieve the status and output of an RPA job by job ID; poll at sensible intervals to monitor progress without frequent calls.

Instructions

查询影刀任务执行状态与输出。轮询用，不要连续高频调用。

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": {
      "job_id": "<job_id>"
    },
    "name": "rpa_query_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.7.0

TDQS

B3.3/5.0
Behavior3/5

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

There are no annotations, so the description must fully convey behavior. It does disclose that the response contains both status and output, and it includes an anti-rate-limit warning, which is useful context. However, it does not state whether the call is read-only and side-effect free, how a terminal versus running state is represented, or what happens when job_id is unknown or the output is truncated.

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

Conciseness5/5

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

Two short sentences with zero filler. The core purpose is front-loaded, and the polling constraint follows immediately.

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?

This is a simple one-parameter read tool, and the description adequately conveys the purpose and cautions about polling. However, there is no output schema, and the description only minimally describes the return values; provenance for job_id is missing.

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?

There is a single required parameter, job_id, but the schema's description coverage is 0% and the description never explains it. It does not say where job_id comes from (presumably returned by rpa_start_job), its format, or how long it is valid.

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 uses a specific verb and resource: query the execution status and output of a Yingdao (ShadowBot) RPA job. This clearly distinguishes it from the sibling rpa_start_job, but it never names the alternative explicitly.

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?

"轮询用" indicates this tool is for polling a job, and "不要连续高频调用" warns against high-frequency polling. However, it does not say to call it after rpa_start_job, does not name any alternative wait or notification tool, and does not give any concrete polling interval or fallback behavior.

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