Skip to main content
Glama

pls_delete_goods

pls_delete_goods
Destructive

Delete goods entities from the inventory. Requires IDs and explicit confirmation to prevent accidental removal.

Instructions

【🔧 管理】删除物品实体。

参数:

  • confirm: 二次确认(必填),必须传 "确认"

  • ids: ID数组(必填),要删除的实体ID列表

  • 根据实体类型传入对应字段

返回: {success: true/false, entity: 实体名称, action: 操作类型}

提示: 删除不可撤销!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo物品ID(更新/删除时必填,长整型以字符串传入)
idsYes要删除的实体ID列表(长整型以字符串传入)
codeNo物品编号
nameNo物品名称
confirmYes⚠️ 写操作需二次确认,必须传 "确认"
Behavior4/5

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

Annotations already indicate the tool is destructive and not read-only. The description adds that a confirmation string '确认' is required and stresses that deletion cannot be undone, which provides useful behavioral context beyond 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.

Conciseness4/5

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

The description is relatively concise, with bullet points for parameters and a clear return format. The inclusion of the vague phrase '根据实体类型传入对应字段' slightly detracts but overall it is well-structured and front-loaded.

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?

Given no output schema, the description provides a return format which is helpful. However, it does not mention the 'id' parameter from the schema, and the entity-specific fields hint is under-specified. This leaves gaps in completeness for a deletion tool with multiple parameters.

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?

The schema covers all parameters, but the description explains the 'confirm' parameter must be '确认' and lists 'ids' as required. However, the hint about entity-specific fields is unclear and not reflected in the schema, which may mislead. Overall, adds some meaning but introduces ambiguity.

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 clearly states the tool deletes item entities (删除物品实体). It also includes a warning that deletion is irreversible, which adds clarity. However, the vague mention of '根据实体类型传入对应字段' could cause confusion.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like pls_create_goods or other delete tools. There is no mention of prerequisites or conditions for use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sweet-dog-cyber/pls-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server