Skip to main content
Glama

add_click_link

Adds a click-to-open-link interaction to named, non-interactive widgets in Axure RP prototypes, letting you wire links without manually editing the widget.

Instructions

给无交互的具名元件添加点击打开链接交互(capabilities.md 未列此工具,仅结构级)。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 structure,只适用 capabilities.md 的已验样本。CLI: node add-click-link.mjs source.rp output.rp widgetName url [current|new]

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": "add_click_link"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already mark this tool as a non-read-only, non-destructive, non-open-world mutation. The description adds context beyond the annotations: explicit paths do not advance the session chain, and the tool's evidence is logged as structure and is limited to capabilities.md-verified samples. It does not say what happens on failure, whether an existing link is overwritten, or what the tool returns.

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 there is little filler, but the remaining text is tangled: session-chain rules, evidence-logging rules, and a CLI invocation are compressed into dense clauses. Sentences like '具名调用省略宿主源/输出即使用会话链' require re-reading, and there is no separation between constraints and invocation examples.

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?

No output schema exists, and the tool is a two-parameter mutation with annotations present. The description covers chain-advancement behavior, evidence logging, and a CLI example, which is reasonably complete. It leaves unstated the return value, conflict or overwrite behavior, and failure modes that an agent would need before calling this tool.

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 description coverage is only 50%: the session parameter is documented in the schema, while the args array is not. The description partially compensates by stating that in session mode, args omits the host source and output, and the CLI line implies the positional order source, output, widgetName, url, and an optional mode. Because it does not pin this order to args, its compensation is only partial.

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: it adds a click-to-open-link interaction to a named widget that currently has no interaction. It also scopes the tool to the structure level. However, it does not distinguish this tool from the sibling tools add_interaction or patch_link_window, so the agent must infer which one to use.

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 gives some conditions: the widget must be non-interactive and named, and the tool applies only to samples already verified in capabilities.md. It also explains when to use session mode versus explicit paths. It never says when to choose add_interaction or patch_link_window instead, so the guidance for using this tool versus its alternatives is only implied.

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