Skip to main content
Glama

verify

Read-only

Re-reads the .rp file or disk chain tail and checks for parse errors, dangling references, and duplicate component names; enable deep mode for detailed issue and traversal statistics.

Instructions

重新读取磁盘链尾(或通过 path/rp/file 指定的 .rp 文件)并校验(包含 GUI 或外部改动):浅查=三零(unparseable/danglingRefs/problems);deep=true 加同页重复名(跨页共享组件同名汇总在 duplicateSummary,传 includeCrossPageDuplicates=true 可展开全部)、悬空引用与问题明细、全页全容器遍历统计。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpNo
deepNo
fileNo
pathNo
rpFileNo
includeCrossPageDuplicatesNo可选:deep=true 时是否返回跨页面共享组件同名元件列表,默认 false(仅返回同页内重名元件)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare this a safe, non-destructive, non-open-world read, so the bar is lower, and the description still adds real behavior: it re-reads from disk (picking up external/GUI edits), enumerates exactly what the shallow pass checks, and explains what deep=true unlocks. It is weaker on cost/latency of the full-page traversal and on how failures are reported beyond a nonzero count.

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 critical scope statement is front-loaded, but the single run-on sentence is dense with jargon and stacked parentheticals, which slows parsing of the deep/shallow distinction. Nothing is obviously removable, yet the information would land better split into a mode line and an output line.

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 read-only validator with six parameters, no required fields, no output schema, and 17% schema coverage, the description does useful work by naming the result keys an agent will get back. It is still incomplete: the return shape is only sketched, and the relationship among the four file-locator parameters is unresolved, which is the main thing an agent must decide before calling.

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 coverage is low at 17%, so the description must carry parameter meaning, and it does explain deep and includeCrossPageDuplicates (including the default false and that expansions land in duplicateSummary). However, it never disambiguates the three overlapping input sources path/rp/file, and rpFile is not mentioned at all — an agent cannot tell which of the four file-locator parameters takes precedence. This only partly compensates for the coverage gap.

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+resource pair: re-read the disk chain tail (or a .rp file given by path/rp/file) and validate it, explicitly including out-of-band GUI/external edits. It also names the concrete check categories (unparseable/danglingRefs/problems) rather than speaking in generalities. It does not distinguish itself from look-alike siblings such as inspect, diagnose_prototype, or axvg_selftest, so it falls short of a 5.

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?

The shallow-vs-deep split is effectively a usage rule: skip deep for the three zero-checks, set deep=true only when you also want same-page duplicate names, dangling-ref detail, and full-container traversal stats. What is missing is any statement of when to reach for verify rather than inspecting/diagnosing siblings, and any prerequisite (for example, that a project must already be on disk) is left implicit.

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