Skip to main content
Glama
Sign In
AgentRPA

AgentRPA

by c8xm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rpa_list_apps

Lists YingDao RPA apps or workflows, optionally filtered by name, so you can retrieve an appId before choosing and running a process.

Instructions

列出影刀应用（RPA 流程）。先查这个拿到 appId，再决定跑哪个流程。

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": "rpa_list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordNo按名称过滤，可空

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.7.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden on its own. "列出" and "拿到 appId" correctly signal a read-only listing that returns app identifiers, but nothing is said about pagination, result volume, permissions, or how many apps come back.

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 no filler; the purpose comes first and the workflow constraint follows. Every sentence carries information the agent needs.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter listing tool with no annotations or output schema, the description covers what the tool is and where it sits in the workflow. Only the shape of the returned app list is left implicit, which is a minor gap given the tool's simplicity.

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 100%, so the single optional keyword filter is already documented by the schema. The description adds no extra meaning about filtering syntax or matching behavior, making the baseline of 3 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?

"列出影刀应用（RPA 流程）" gives a specific verb (list) and resource (Yingdao/RPA apps), immediately clarifying it is a read/list operation. It does not name any sibling tools directly, but the mention of appId positions it relative to the run tool.

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

Usage Guidelines4/5

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

"先查这个拿到 appId，再决定跑哪个流程" explicitly states when to use it: as a first step before choosing which flow to run, implicitly pointing to rpa_start_job. It stops short of naming that alternative or stating any exclusions.

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