Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

当前选区明细

vtable_get_selection
Read-only

Retrieve detailed cell information from the currently selected VTable region, including column, row, field, title, value, and full record data, to support assertions after selection.

Instructions

读取 VTable 当前选区的单元格明细：col/row/field/title/value 及完整业务记录 originData。点击/框选单元格后用它做断言（数据源为官方 getSelectedCellInfos）。

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

Input Schema

NameRequiredDescriptionDefault
tab_idNo
table_indexNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint annotation is reinforced by the description's read action and no side effects. It adds transparency by naming the official data source getSelectedCellInfos and the intended assertion use.

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

Conciseness5/5

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

The description is one concise sentence with no fluff, front-loading the action and then providing useful output/usage details.

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?

It covers purpose, output fields, and intended usage, but omits any explanation of the optional parameters tab_id and table_index, which an agent may need to target the correct VTable instance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The two parameters tab_id and table_index have no schema descriptions and are not mentioned in the tool description. With 0% schema description coverage, the description fails to compensate by explaining what these parameters identify.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action (read current selection details) and resource (VTable current selection), and includes output fields. It clearly distinguishes from sibling VTable tools by focusing on the active selection.

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?

Explicitly says to use it after clicking or box-selecting cells for assertions, giving a clear usage moment. It does not name alternative tools or negative conditions, but the selection scope implies when it applies.

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