Skip to main content
Glama

面灵AI 面试助手

delete_knowledge_base_entry

Destructive

删除知识库中的一条问答。条目 ID 取自 get_knowledge_base。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 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_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes条目 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new context: the operation is irreversible, requires an explicit user-consent step, and requires the interviews:write authorization scope. Irreversibility partly overlaps with the destructive annotation, which keeps it from a 5.

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?

Four compact sentences, front-loaded with the action, then ID provenance, then the risk/consent rule, then the auth scope. No filler and nothing buried.

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 single-parameter destructive tool with no output schema and annotations already covering the safety profile, the description supplies everything needed: target, ID origin, irreversibility, consent workflow, and required 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?

Schema coverage is 100% for the single id parameter, so the schema already defines the type and constraint; the description still adds provenance by saying the ID must be sourced from get_knowledge_base, which meaningfully guides correct value selection.

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 names a specific verb and resource ("删除知识库中的一条问答" — delete a single Q&A entry in the knowledge base), which distinguishes it from the sibling delete_knowledge_base that removes a whole base. An agent can tell exactly what gets removed without opening the schema.

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 explicitly states where the ID comes from (get_knowledge_base) and adds a mandatory pre-execution step of explaining the content and obtaining user consent. It does not name alternatives such as update_knowledge_base_entry for modification-only cases, so it stops short of a full when/when-not routing.

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