Skip to main content
Glama

rp_read

Read-only

Parse a .rp prototype read-only to extract page, widget, and interaction summaries or JSON, including dangling reference checks, without modifying the source file.

Instructions

只读解析 .rp 输出页面/元件/交互摘要或 JSON(含 dangling refs 检查)。具名调用省略宿主源/输出即使用会话链;原始 args 用 session:true 并省略这两个参数(多源工具保留导入源)。显式路径不推进链。 登记证据 structure,只适用 capabilities.md 的已验样本。CLI: node rp-read.mjs <file.rp> [--json] [--full]

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and a closed world, so the safety profile is covered. The description adds genuinely non-obvious behavior — that explicit paths do not advance the session chain while named calls do, that dangling refs are checked, and that evidence registration only applies to verified samples in capabilities.md — but leaves the opaque '登记证据 structure' obligation unexplained.

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?

Front-loaded with purpose and mode rules, but sentences are densely packed with internal jargon (链, 宿主源, 登记证据 structure) that reads as notes for an insider rather than agent instructions. The trailing CLI line is useful but the register-evidence clause is cryptic and could be cut or clarified.

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, so the description does the work of naming the output forms (summary vs JSON, --full) and the dangling-refs check, which is adequate for a read-only tool. However the evidence-registration requirement has no explanation of what it means or how to satisfy it, leaving a real operational gap.

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 100%, yet the description adds meaning the schema does not: the positional <file.rp>, the --json/--full CLI flags, and the rule that with session:true the args array must omit host source and output (multi-source tools still pass the import source). The remaining gap is that the loosely described evidence-registration argument is not mapped to any schema field.

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?

States a specific verb and resource: read-only parse of a .rp file producing page/component/interaction summaries or JSON, plus a dangling-refs check. That distinguishes it from mutation siblings like axure_save or add_interaction, though it never names the closest read alternatives such as read_interactions or inspect.

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?

Gives real mode-selection rules: named invocation omits host source/output and uses the session chain, raw args use session:true with those two params omitted, and explicit paths do not advance the chain. It stops short of saying when to prefer a sibling read tool over this one.

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