Skip to main content
Glama
the-real-talk

the-real-talk

set_reactions

Replace a node's prototype reactions to define triggers and actions for click, hover, timeout, navigation, transitions, and variant hover behavior.

Instructions

Replace the prototype reactions of a node. Each reaction: { trigger: {type: ON_CLICK|ON_HOVER|ON_PRESS|ON_DRAG|AFTER_TIMEOUT|MOUSE_ENTER|MOUSE_LEAVE|MOUSE_UP|MOUSE_DOWN, timeout?, delay?}, actions: [{type: NODE|BACK|CLOSE|URL, destinationId?, navigation?: NAVIGATE|CHANGE_TO|OVERLAY|SWAP|SCROLL_TO, transition?: {type: SMART_ANIMATE|DISSOLVE|MOVE_IN|PUSH|SLIDE_IN, duration (seconds), easing: {type: EASE_IN|EASE_OUT|EASE_IN_AND_OUT|LINEAR|...}}, url?}] }. For variant hover, put ON_HOVER with CHANGE_TO on a variant component and point to the hover variant.

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": {
      "nodeId": "<nodeId>",
      "reactions": "<reactions>"
    },
    "name": "set_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
reactionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully states that reactions are replaced rather than appended and explains the reaction payload format, but omits permissions, whether an empty array clears reactions, return behavior, and error conditions.

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?

The purpose is front-loaded, and the dense inline schema is efficient for a complex payload. It is somewhat run-on and uses "..." incompletely in enum examples, but most content earns its place.

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

Completeness4/5

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

For a complex nested reactions payload with no output schema or annotations, the description gives substantial structural detail and a variant-hover tip. It still misses nodeId semantics, the 20-item limit, empty-array behavior, and return/error context.

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 description coverage is 0%, and the description compensates strongly for reactions by detailing trigger types, action types, navigation options, transitions, and variant-hover usage. However, nodeId is left unexplained beyond the schema's type and minLength.

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 states a specific verb and resource: "Replace the prototype reactions of a node." This clearly identifies a mutation tool for reactions, though it does not explicitly contrast with the sibling get_reactions.

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?

It provides a useful scenario for variant hover interactions, but does not explain general when-to-use guidance versus get_reactions, prerequisites, or when not to use this tool.

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