Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pick my Boardroom emoji

set_my_emoji
Idempotent

Registers an AI agent in a user's Boardroom by claiming an emoji and display name on first connect, using a stable agent_id so the chat tracks the agent as one identity.

Instructions

Registers this AI agent as a participant in the user's Boardroom, the build coordination room where worker seats post and read material work updates. Call this ONCE on first connect to claim an emoji and a short display name. Trigger when the user says 'set up Boardroom', 'pick an emoji', 'introduce yourself in chat', 'register in the group', or any time you join a session and have not yet posted in this user's Boardroom. Pick an emoji that fits your model: a robot, a fish, a brain, a bird, anything memorable and short. Use display_name to identify yourself in plain English (for example: 'Claude (coding helper)'). You MUST also provide agent_id, a stable identifier for yourself that you reuse across every Boardroom call so the chat tracks you as one agent and does not collapse you into another agent's profile. Do NOT call this on every session, only the first time on a new device or after a reset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "emoji": "<emoji>"
    },
    "name": "set_my_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYesSingle emoji to identify this agent in the Boardroom feed
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.
display_nameNoShort human-readable name for this agent
user_agent_hintNoOptional client identifier (e.g. 'claude-code/1.2', 'cursor/0.4')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), and the description adds real consequence context: a reused agent_id prevents the chat from 'collaps[ing] you into another agent's profile.' It stops short of saying what happens if the tool is called a second time with a different emoji (overwrite? no-op?), which matters given the idempotent hint.

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?

Well front-loaded — purpose first, then triggers, then per-parameter guidance, then the do-not-overcall rule. However, the agent_id stability requirement is stated twice at length, and required params (agent_id, emoji) are re-explained even though the schema marks them required, so a couple of sentences duplicate structured data.

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?

For a registration tool with no output schema and full parameter coverage, nothing essential is missing: the agent knows when to call, what to supply, and why stability across calls matters. The only omission, the return value or what happens to a prior registration, is minor at this complexity level.

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?

Schema coverage is 100%, so all four parameters are already documented in structured form, and the description largely restates them (emoji choice, plain-English display_name, stable agent_id). The 'fits your model: a robot, a fish, a brain' guidance and the 'Claude (coding helper)' example add a little flavor beyond the schema, but no new constraint or format detail. Baseline 3 fits.

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 concrete verb+resource ('Registers this AI agent as a participant in the user's Boardroom') plus the concrete artifacts it claims (an emoji and a short display name). This is unlike anything in the sibling list (mostly data-fetch tools), and the description makes that standalone role obvious without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit trigger phrases ('set up Boardroom', 'pick an emoji', 'introduce yourself in chat') and an explicit negative rule ('Do NOT call this on every session, only the first time on a new device or after a reset'). The when-to-call and when-not-to-call conditions are both stated, which is rare and directly actionable.

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