uc-remote-mcp

Overview Schema Source Related Servers Discussions Admin

create_activity

Creates a new activity for the Unfolded Circle Remote home screen by selecting entities or cloning an existing activity, removing the empty page and reporting group membership.

Instructions

Create an activity — a "device" on the remote's home screen.

Pass entity_ids to build from scratch, or clone_from to copy an existing activity/macro/remote-entity; not both. icon takes "uc:name" or "custom:file.png". The empty page the remote creates alongside it is removed, and the result says if it joined the default activity group, which can make its tile power devices on and off.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`host`	No
`icon`	No
`name`	Yes
`dry_run`	No
`clone_from`	No
`entity_ids`	No
`description`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.1Sep 20, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses side effects: the empty page is removed, and the result indicates whether the activity joined the default group and may control device power. It does not mention the dry_run default, but the schema exposes that parameter.

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 compact and front-loaded: definition first, then construction modes, then side effects. Every sentence adds useful information with no redundancy or 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?

The description covers the main creation paths and a key side effect, and an output schema exists for return values. However, the critical dry_run default is unexplained, and there is no guidance for the optional host parameter, leaving an agent without full context for a 7-parameter tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It explains entity_ids, clone_from, and icon, but not host, description, or dry_run. The dry_run parameter is especially important because it defaults to true, yet the description is silent about its meaning.

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 opens with a specific verb and resource: 'Create an activity' on the remote's home screen. It distinguishes the tool from siblings like list_activities and get_activity by making clear this is the creation operation.

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?

It gives explicit construction guidance: use entity_ids for building from scratch, clone_from for copying, and not both. It lacks explicit comparison to alternative sibling tools, but the within-tool usage decision is clearly described.

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