Skip to main content
Glama
ying-dao

YingDao RPA MCP Server

Official
by ying-dao

runApp

Execute RPA applications using the YingDao RPA MCP Server by specifying the appUuid and optional parameters to automate repetitive tasks efficiently.

Instructions

该接口用于运行RPA应用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appParamsNoschema.local.executeRpaApp.appParams
appUuidYesschema.local.executeRpaApp.appUuid

Implementation Reference

  • Registers the 'runApp' MCP tool with description, input schema, and an inline async handler that delegates to LocalService.executeRpaApp and formats the response.
    this.server.tool('runApp', i18n.t('tool.runApp.description'), executeRpaAppSchema, async ({ appUuid, appParams }) => {
        try {
            const result = await this.localService?.executeRpaApp(appUuid, appParams);
            return { content: [{ type: 'text', text: JSON.stringify(result) }]};
        } catch (error) {
            throw new Error(i18n.t('tool.runApp.error'));
        }
    });
  • Defines the Zod input schema for the runApp tool: appUuid (required string) and appParams (any).
    export const executeRpaAppSchema = {
        appUuid: z.string().describe(i18n.t('schema.local.executeRpaApp.appUuid')),
        appParams: z.any().describe(i18n.t('schema.local.executeRpaApp.appParams'))
    } as const;
  • Implements the core logic of running the RPA app by constructing an argv string with the appUuid and spawning the shadowbot process (note: appParams is unused).
    async executeRpaApp(appUuid: string, appParams: any) {
        let argv = `shadowbot:Run?robot-uuid=${appUuid}`;
        spawn(this.shadowbotPath, [argv]);
        return 'success';
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool runs an RPA application but does not describe behavioral traits such as whether it's a read-only or destructive operation, authentication needs, rate limits, execution time, or error handling. This is a significant gap for a tool that likely performs mutations, making it inadequate for safe agent use.

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?

The description is a single, efficient sentence in Chinese: '该接口用于运行RPA应用。' (This interface is used to run RPA applications.) It is front-loaded and wastes no words, making it highly concise. Every part of the sentence contributes to the core purpose without redundancy.

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?

Given the complexity of running an application (likely a mutation), the lack of annotations, no output schema, and sibling tools that suggest a workflow (e.g., queryApplist to get appUuid), the description is incomplete. It does not cover execution behavior, return values, error cases, or integration with other tools, leaving critical gaps for agent operation.

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?

The schema description coverage is 100%, with parameters appUuid (required, string) and appParams (optional, no type specified). The description adds no meaning beyond the schema, as it does not explain what appUuid or appParams represent (e.g., appUuid as an identifier from queryApplist, appParams as configuration). With high schema coverage, the baseline is 3, but the description fails to compensate for the lack of semantic clarity in the schema descriptions, which are generic placeholders.

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

Purpose3/5

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

The description states the tool's purpose as '运行RPA应用' (run RPA application), which is a clear verb+resource combination. However, it lacks specificity about what '运行' entails (e.g., execution, deployment, testing) and does not distinguish it from sibling tools like queryApplist or queryRobotParam, which appear to be query tools rather than execution tools. The purpose is understandable but vague in scope.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing an appUuid from queryApplist, or exclusions, like when not to run an app. There is no reference to sibling tools or contextual cues for usage, leaving the agent with minimal direction.

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

Related 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