Skip to main content
Glama
Sign In
YingDao RPA MCP Server

YingDao RPA MCP Server

Official
by ying-dao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

queryClientList

Retrieve a filtered list of RPA robots by status, keyword, or group UUID. Supports pagination to control output size for efficient robot management.

Instructions

该接口用于查询RPA机器人列表。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "queryClientList"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo状态,idle表示空闲,一般不指定关键字的情况下都是要查询空闲的机器人
keyNo关键字
robotClientGroupUuidNoRPA机器人组uuid
pageNo页码1
sizeNo一页大小30

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits like read-only nature, required permissions, or side effects. For a query tool, read-only is implied but not stated.

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?

A single sentence is concise and avoids verbosity, but it is overly terse given the tool has 5 parameters.

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?

The description is minimal but covers the basic purpose. Without output schema, more detail on return values or pagination behavior would improve completeness.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds no extra meaning beyond what the schema already provides.

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 'query list of RPA robots,' which is a specific verb and resource. However, it does not distinguish it from sibling tools like queryApplist.

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 on when to use this tool versus alternatives (e.g., queryApplist, queryRobotParam), nor any prerequisites or context provided.

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