UiPath MCP Server

uipath_get_robots

List UiPath Orchestrator robots, optionally filtered by folder, to identify and manage your automation fleet.

Instructions

Get robots from UiPath Orchestrator with optional folder filtering.

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

Input Schema

Name	Required	Description
`skip`	No	Number of items to skip (default 0)
`limit`	No	Maximum items to return (default 50)
`folderId`	No	Optional folder ID filter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get robots' and 'optional folder filtering,' but does not mention pagination behavior, return format, authentication needs, or confirm that the operation is purely read-only. It adds minimal behavioral context beyond the name and schema.

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, front-loaded sentence that states the purpose without any unnecessary words or repetition. It is concise and immediately understandable.

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 tool is a simple read operation with three optional parameters and no output schema. The description is adequate for understanding its basic function but lacks details on response format, default pagination behavior, or any caveats about folder filtering. Given the simplicity and the schema's thorough parameter descriptions, a mid-range score is appropriate.

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 input schema already provides descriptions for all three parameters (skip, limit, folderId) with 100% coverage. The description's mention of 'optional folder filtering' aligns with the folderId parameter but does not add 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.

Purpose5/5

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

The description clearly states 'Get robots from UiPath Orchestrator' with a specific verb, resource, and context. It also mentions 'optional folder filtering,' which adds scope and distinguishes it from sibling tools that retrieve queue items, 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 Guidelines3/5

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

The description implies the tool is used to retrieve robots from UiPath Orchestrator, and the mention of folder filtering hints at a specific use case. However, it provides no explicit guidance on when to prefer this tool over alternatives or any excluded scenarios.

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