Skip to main content
Glama

面灵AI 面试助手

delete_knowledge_base

Destructive

删除一份面试知识库(含其中全部问答)。知识库 ID 取自 list_knowledge_bases。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 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_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes知识库 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, and the description goes well beyond them: it discloses the cascading effect (all contained Q&A are removed), irreversibility ('删除后不能恢复'), a required user-consent step, and the authorization scope interviews:write. These are precisely the behavioral facts an agent needs before calling a destructive tool.

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?

Front-loaded with the destructive scope, then the ID source, then the irreversibility/consent warning, then the auth scope. Every clause carries information an agent would otherwise have to infer; nothing is redundant with the title or schema.

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, the description covers cascade semantics, irreversibility, consent requirement, ID provenance, and auth scope. Nothing material to a correct invocation is missing.

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 is fully documented in the schema (100% coverage), so the schema baseline carries most weight. The description adds real value by stating the provenance of that ID (from list_knowledge_bases), which tells the agent how to source a valid value rather than guessing.

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 verb and resource ('删除一份面试知识库') plus the scope of the deletion ('含其中全部问答'), which is exactly what separates it from the entry-level sibling delete_knowledge_base_entry. An agent knows this removes the container and its contents, not a single Q&A pair.

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?

Gives a concrete precondition chain: obtain the ID from list_knowledge_bases, explain the deletion target to the user, and obtain consent before executing. It does not explicitly name delete_knowledge_base_entry as the alternative for single-entry removal, so the when-not guidance is implied rather than stated.

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