Skip to main content
Glama
vino3dx
by vino3dx

deselect_all

Read-only

Clear the active selection before batch operations to prevent unintended modifications to previously selected objects.

Instructions

清空当前选择。批量操作前先清空可避免误伤上一次选择的对象。 [English] Clear the current selection. Useful before a batch operation so you do not accidentally operate on whatever was selected earlier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the rationale (preventing accidental operations on a previous selection), which is useful context but not extensive. It does not contradict the annotations.

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 concise, with two short sentences in English (plus a Chinese duplicate). It front-loads the action and then provides the usage rationale. Every word earns its place, and it is well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema tool with annotations covering safety, the description provides sufficient information: what it does, when to use it, and why. No additional details are needed for an agent to invoke it correctly.

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?

There are no parameters, so the schema is fully descriptive. The baseline is 4 for tools with 0 parameters; the description does not need to add parameter details and appropriately omits them.

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?

The description explicitly states 'Clear the current selection' – a clear verb and resource. It differentiates from siblings like select_all and select_objects by implying it deselects all, and the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit usage guidance: 'Useful before a batch operation so you do not accidentally operate on whatever was selected earlier.' This tells the agent when to call it, which is particularly valuable given the context of many sibling tools that operate on the current selection.

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