Skip to main content
Glama

面灵AI 面试助手

delete_hot_word_library

Destructive

删除一个自建热词库,已绑定它的岗位随之解除绑定。词库 ID 取自 list_my_hot_words。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 interviews:write)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_hot_word_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond destructiveHint=true, the description discloses the cascade side effect (bound positions are unbound), irreversibility ('删除后不能恢复'), the required consent workflow, and the auth scope (interviews:write). These are exactly the behavioral facts the annotations cannot convey.

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?

Sentences are front-loaded with the action and side effect, then prerequisites. Four short clauses each carry distinct information, though the parenthetical auth-scope note is slightly bolted-on and could sit more naturally alongside the consent requirement.

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 one-parameter destructive tool with no output schema, everything an agent needs to act safely is present: what is deleted, what else changes, irreversibility, consent gating, ID source, and permission scope.

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?

The single `id` parameter has no schema description (0% coverage), but the description compensates by telling the agent where to source a valid value (list_my_hot_words) and establishing it identifies a self-built library. It does not state the ID format or error behavior for unknown IDs.

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 states a specific verb+resource pair ('删除一个自建热词库') and qualifies the scope as user-created libraries, which distinguishes it from the sibling create/update/list hot-word tools without needing to open their schemas.

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 gives concrete preconditions for use: the ID must come from list_my_hot_words, and the agent must explain the deletion and obtain user consent first. It stops short of naming an explicit alternative or when-not-to-use condition, so it is strong guidance but not a full routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources