Skip to main content
Glama

add_adaptive_view

Adds Base and breakpoint subviews to an Axure page, then applies per-view component width, height, and position overrides.

Instructions

为页面写入自适应视图集(Base+子视图)并按视图覆盖元件尺寸位置。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 gui-roundtrip,只适用 capabilities.md 的已验样本。CLI: node add-adaptive-view.mjs <src.rp> <out.rp> [断点宽度...] [--override "<视图名>:<元件名>:w=<宽>[,h=<高>][,x=,y=]"]

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_adaptive_view"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-open-world write operation. The description adds meaningful behavioral context beyond that: session-chain usage, explicit paths not advancing the chain, and applicability limited to verified samples in capabilities.md. It still does not explain overwrite semantics for existing views or any failure behavior.

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?

The purpose is front-loaded and the text is not long, but it is a dense run-on paragraph that mixes purpose, session-chain rules, evidence restrictions, and CLI syntax. It would be easier to parse if separated into purpose, usage, and argument sections.

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?

For a mutating tool with no output schema, the description covers invocation and argument structure well. However, it omits important side-effect details such as whether existing adaptive views are replaced, what confirmation is returned, and how errors are surfaced.

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 only 50%, so the description must compensate for the undocumented args array. It does so by giving CLI positional arguments for source/output, optional breakpoint widths, and --override syntax mapping view, widget, width, height, and x/y values, as well as explaining the session flag. The mapping is strong though not exhaustive about ordering or escaping.

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: writing an adaptive view set (Base plus subviews) to a page and overriding widget size/position per view. It is clearly more specific than the tool name alone, though it does not differentiate this tool from any sibling alternatives.

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 explains invocation modes: named calls omit host source and output to use the session chain, raw args use session:true, and explicit paths do not advance the chain. It also restricts applicability to verified samples in capabilities.md, but it never states when to choose this tool over related tools such as other view-building or interaction tools.

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