UiPath MCP Server

uipath_get_count_stats

Retrieve total counts of Processes, Assets, Queues, and Schedules in UiPath Orchestrator for a quick overview of your automation inventory.

Instructions

Gets the total number of various entities registered in Orchestrator (Processes, Assets, Queues, Schedules).

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_count_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It mentions the tool 'Gets' counts but does not specify the return format, whether counts are broken down by folder, or any limitations. This leaves significant ambiguity about the output structure.

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 sentence that is direct, specific, and well-structured. Every word contributes to understanding the tool's purpose without unnecessary filler.

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?

For a simple tool with no parameters and no output schema, the description provides a basic understanding of purpose and entity examples. However, it is ambiguous whether 'total number' means a single aggregate or separate counts per entity, and it does not describe the exact response format, leaving some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, and the schema coverage is trivially 100%. The description adds value by clarifying what the tool returns (counts of entities), which goes beyond the empty schema. This meets the baseline of 4 for zero-parameter tools.

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 the tool gets total counts of Orchestrator entities, with specific examples (Processes, Assets, Queues, Schedules). It distinguishes from sibling tools that retrieve individual items, making the purpose reasonably clear.

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 is provided on when to use this tool versus the many sibling get_* tools. The description only explains what it does, not in which scenarios it should be preferred over alternatives like uipath_get_queue_items or uipath_get_jobs.

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