vtable_scroll_to_cellScroll a virtual-scrolling VTable to bring a specified cell into view using row and column coordinates.
把 VTable 滚动到指定单元格使其进入可视区域（支持虚拟滚动）。
| Name | Required | Description | Default |
|---|---|---|---|
| col | Yes | ||
| row | Yes | ||
| tab_id | No | ||
| table_index | No |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| message | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint=true annotation is consistent with the described scroll behavior; no mutation or destructive side effect is implied. The description directly communicates the tool's visible effect, which is appropriate for a read-only viewport adjustment.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no filler or redundant information. It states the primary action and an important supporting detail about virtual scrolling.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value details are not mandatory. However, the description lacks parameter-level context and does not distinguish when to use this tool versus related vtable scrolling tools, leaving only moderate completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain the meaning of col, row, tab_id, or table_index. The agent must infer coordinate semantics and optional targeting behavior without any supporting detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('scroll') and the resource ('VTable' to a specified cell), with the goal of bringing that cell into the visible area. It does not explicitly name the sibling tool vtable_scroll_viewport, but the cell-specific target distinguishes it well enough.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to choose this tool over vtable_scroll_viewport or other vtable navigation tools. The description mentions virtual scrolling support but does not explain practical use cases or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.