Skip to main content
Glama

inspect

Read-only

View a single element's rich-text runs, fonts, colors, links, geometry, and expanded interaction tree; locate it by query/name/page/record/id or read a specified .rp file.

Instructions

单元件深看:富文本段落/runs 明细(字体/字号/样式/颜色/链接目标)、几何、交互树人类可读展开。target 接受 locate 返回的定位字段(也可直接在顶层传 query/name/page/record/id);可选传 path/rp/file 直接只读查看指定 .rp。

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

Input Schema

NameRequiredDescriptionDefault
idNo
rpNo
fileNo
nameNo
pageNo
pathNo
typeNo
queryNo
recordNo
rpFileNo
targetNolocate 返回的定位字段对象(record+id [+container] 精确定位)或 {query[,page][,type]} 搜索(须唯一)或字符串(按名称/文本搜)
containerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description still adds real value by disclosing the shape of the result — three categories of data, including a human-readable expansion of the interaction tree — and by flagging that the .rp path mode is read-only viewing. It does not discuss failure conditions such as the uniqueness requirement for query-based targeting.

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

Conciseness4/5

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

Two dense sentences: the first front-loads what gets inspected, the second handles parameter routing and the alternate mode. Given 12 parameters the length is justified, and semicolons keep it compact, though the parenthetical field list is slightly crowded.

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 12-parameter tool with near-zero schema coverage and no output schema, the description does well to explain the return categories and the two invocation modes. Gaps remain: the meaning of type and container, the relationship/precedence between top-level fields and the target object, and the uniqueness constraint for query-based lookup are not covered in the description.

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 8% across 12 parameters, so the description must carry most of the semantic load — and it does explain the two targeting modes (locate-derived object vs. top-level query/name/page/record/id) and the path/rp/file viewing mode, naming roughly ten of the twelve parameters. However, type, rpFile, and container are left unaddressed, and no precedence rules between the direct and target forms are given.

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 names a specific operation on a specific resource — deep inspection of a single widget — and enumerates what it surfaces: rich-text paragraph/run details (font, size, style, color, link target), geometry, and a human-readable interaction tree. Its reference to 'locate 返回的定位字段' implicitly separates it from the sibling locate tool (locate finds, inspect drills down), though it never states the contrast outright.

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 establishes a clear workflow: call locate first, then pass its returned positioning fields, or supply query/name/page/record/id at the top level. It also names an alternative mode — passing path/rp/file to view a .rp read-only. There are no explicit exclusions or when-not-to-use statements, so it falls short of a 5.

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