Skip to main content
Glama
ying-dao

YingDao RPA MCP Server

Official
by ying-dao

queryApplist

Retrieve a paginated list of RPA applications using filters like app ID, name, or owner. Query to browse and select automation tasks.

Instructions

该接口用于分页获取RPA应用列表。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoRPA应用UUID
sizeNo一页大小30
pageNo页码1
ownerUserSearchKeyNo用户账号精确匹配
appNameNoRPA应用名称模糊匹配

Implementation Reference

  • Registration of the queryApplist tool for local mode. Calls this.server.tool('queryApplist', ...) with the local queryAppList schema and handler.
    registerLocalTools(): void{
        this.server.tool('queryApplist', i18n.t('tool.queryApplist.description'), querySchema, async ({ appId, size, page, ownerUserSearchKey, appName }) => {
            try {
                const result = await this.localService?.queryAppList();
                return { content: [{ type: 'text', text: JSON.stringify(result) }]};
            } catch (error) {
                throw new Error(i18n.t('tool.queryApplist.error'));
            }
        });
  • Registration of the queryApplist tool for OpenAPI mode. Calls this.server.tool('queryApplist', ...) with the querySchema and handler that calls openApiService.queryAppList().
    this.server.tool('queryApplist', i18n.t('tool.queryApplist.description'), querySchema, async ({ appId, size, page, ownerUserSearchKey, appName }) => {
        try {
            const result = await this.openApiService?.queryAppList({
                appId,
                size,
                page,
                ownerUserSearchKey,
                appName
            });
            return { content: [{ type: 'text', text: JSON.stringify(result) }]};
        } catch (error) {
            throw new Error(i18n.t('tool.queryApplist.error'));
        }
    });
  • Handler for queryApplist in local mode (lines 42-48). Async callback that calls this.localService?.queryAppList() and returns the result as JSON.
    this.server.tool('queryApplist', i18n.t('tool.queryApplist.description'), querySchema, async ({ appId, size, page, ownerUserSearchKey, appName }) => {
        try {
            const result = await this.localService?.queryAppList();
            return { content: [{ type: 'text', text: JSON.stringify(result) }]};
        } catch (error) {
            throw new Error(i18n.t('tool.queryApplist.error'));
        }
  • Handler for queryApplist in OpenAPI mode (lines 88-100). Async callback that calls this.openApiService?.queryAppList({...}) with appId, size, page, ownerUserSearchKey, appName params.
    this.server.tool('queryApplist', i18n.t('tool.queryApplist.description'), querySchema, async ({ appId, size, page, ownerUserSearchKey, appName }) => {
        try {
            const result = await this.openApiService?.queryAppList({
                appId,
                size,
                page,
                ownerUserSearchKey,
                appName
            });
            return { content: [{ type: 'text', text: JSON.stringify(result) }]};
        } catch (error) {
            throw new Error(i18n.t('tool.queryApplist.error'));
        }
  • querySchema used by the OpenAPI registration of queryApplist. Defines appId, size, page, ownerUserSearchKey, appName params with defaults and transforms.
    export const querySchema = {
        appId: z.string().optional().describe(i18n.t('schema.query.appId')),
        size: z.string()
        .optional()
        .default('30')
        .transform(Number)
        .describe(i18n.t('schema.query.size')),
        page: z.string()
        .optional()
        .default('1')
        .transform(Number)
        .describe(i18n.t('schema.query.page')),
        ownerUserSearchKey: z.string().optional().describe(i18n.t('schema.query.ownerUserSearchKey')),
        appName: z.string().optional().describe(i18n.t('schema.query.appName'))
    } as const;
Behavior2/5

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

With no annotations, the description must carry full burden. It only states basic purpose of paginated listing. No disclosure of rate limits, authentication, ordering behavior, or error conditions. Lack of behavioral details limits transparency.

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?

Single sentence, no unnecessary words. Front-loaded with core purpose. Highly efficient.

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?

For a paginated list tool with 5 parameters, the description is too brief. It does not explain return structure, default ordering, or how pagination works. More context is expected despite good schema coverage.

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 coverage is 100% with parameter descriptions. Description does not add extra meaning beyond what is in the schema; it just paraphrases the pagination concept. Baseline score of 3 is appropriate.

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

Purpose5/5

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

Description clearly states it is for paginated retrieval of RPA app list. Uses specific verb '分页获取' (paginate and get) and resource 'RPA应用列表'. Different from sibling tools which operate on different resources (clients, jobs, etc.).

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. No mention of prerequisites, exclusions, or context such as required permissions. Single sentence does not address usage conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ying-dao/yingdao_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server