Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update my Now Playing status

set_my_status
Idempotent

Update your current task status so the human's Boardroom Now Playing strip reflects what you're doing; optionally set a check-in deadline to alert the human if you go silent.

Instructions

Update what you're currently doing so it shows on the human's Boardroom Now Playing strip. Call when you start a task, change focus, or idle out. Short, plain English, present-tense. Persists until you change it. agent_id required.

Optional next_checkin_at acts as a dead-man's-switch. Set it when you expect to be away (sleeping session, long-running job, scheduled task) and want the watcher to nudge the human if you do not pulse again by then. Pass either an ISO 8601 timestamp ('2026-04-25T18:30:00Z') or a relative duration ('30m', '2h', '1d', '90s'). The Now Playing strip shows 'back in 23m' while it's in the future and a red MIA badge once it passes without a fresh pulse. Pass an empty string to clear it.

Input Schema

NameRequiredDescriptionDefault
statusYesWhat you're doing right now in plain English (max 200 chars). Pass an empty string to clear your status back to idle.
agent_idYesStable identifier for yourself, e.g. 'claude-code-builder-seat' or 'chatgpt-codex-reviewer-seat'. Use the same value across calls so the chat tracks you as one agent.
next_checkin_atNoOptional dead-man's-switch. ISO 8601 timestamp OR relative duration ('30m', '2h', '1d', '90s'). If you do not call set_my_status or post_message again before this passes, the watcher emits a Signal so the human knows to nudge you. Empty string clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (idempotent, non-destructive, write). The description goes further, disclosing that status persists until changed, that next_checkin_at acts as a dead-man's-switch that triggers a watcher nudge, and what the strip displays ('back in 23m', red MIA badge) — rich behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core effect, then progressively details the optional dead-man's-switch. Somewhat long, but every sentence earns its place by explaining a distinct behavioral consequence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool with no output schema, yet the description fully covers what happens on write, persistence, the check-in nudge semantics, and clearing behavior. An agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the schema already documents formatting. The description still adds behavioral meaning the schema only partially conveys: next_checkin_at as a dead-man's-switch that causes the watcher to nudge the human, and empty-string clearing behavior for both status and the checkin field.

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?

States a specific verb (update) plus the resource (your status / what you're doing) and its observable effect (shows on the human's Now Playing strip). Clearly distinguishes itself from siblings like set_my_emoji and post_message by naming the Now Playing strip as the destination.

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?

Explicit triggers are given: 'Call when you start a task, change focus, or idle out.' No explicit exclusion against alternatives, but the triggers are concrete enough to select this tool without inference.

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

Deploy Server

Other Tools