Skip to main content
Glama

remove_interaction

Removes active events by event type or deletes one active action by case and action index, enabling targeted interaction cleanup in Axure RP prototypes.

Instructions

按事件类型移除活动事件,或按 Case/Action 序号移除单个活动动作。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node remove-interaction.mjs source.rp output.rp <widgetName|pageName> [--page] [--on-page ] --event (--remove-event | --remove-action --case-index --action-index )

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": {
      "args": "<args>"
    },
    "name": "remove_interaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes
sessionNotrue 时 args 省略宿主源和输出,由当前链注入;多源工具仍传导入源。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.9/5.0
Behavior4/5

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

With only readOnly/destructive/openWorld annotations supplied, the description adds substantive behavior: session-chain side effects, the rule that explicit paths do not advance the chain, and a hard constraint to verified samples only. It stops short of stating whether a removed event is recoverable or what happens to actions under a removed event.

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

Conciseness3/5

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

Purpose is front-loaded and each sentence carries information, but the trailing CLI line is a dense wall of flags and bracket syntax that is slow to parse and partially overlaps the prose invocation rules. It earns its place for argument semantics yet hurts readability.

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 two-parameter mutation tool with no output schema, the definition covers mode selection, session-chain semantics, argument layout and applicability limits. Only the result/confirmation behavior and recovery implications are left unstated.

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 50%: the session parameter is documented in the schema but the args array carries no item-level meaning. The CLI form in the description compensates by spelling out the positional source/output/widget/page arguments and the --event, --remove-event, --case-index and --action-index flags, adding real meaning beyond the schema.

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 and distinguishes two operating modes: removing an event by type versus removing a single action by Case/Action index. An agent can tell what is being removed and at what granularity, though it never names the counterpart tool (add_interaction) to sharpen the contrast.

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 invocation-context guidance: named invocation uses the session chain, raw args require session:true with the two host parameters omitted, explicit paths do not advance the chain, and use is restricted to samples already verified in capabilities.md. There are no explicit when-not-to-use exclusions, but the applicability constraint is a real scoping rule.

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