Skip to main content
Glama

AceRound AI Interview Copilot

delete_knowledge_base

Destructive

Delete an interview knowledge base with all its entries. The ID comes from list_knowledge_bases. Deletion cannot be undone; tell the user what will be deleted and get their agreement first. (Requires the user's sign-in with scope 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
idYesKnowledge base 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 flag destructiveHint=true, but the description goes well beyond that: it discloses that all entries are removed along with the base, that the action is irreversible, that explicit user agreement is required first, and that an OAuth scope (interviews:write) is needed. That is exactly the operational context an agent needs before a destructive call.

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 short sentences, front-loaded with the action and scope, then provenance, then the risk/confirmation rule, then the auth requirement. Nothing is redundant or padded.

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 full annotation coverage, the description supplies everything missing: cascade scope, irreversibility, confirmation protocol, and authorization scope. No gap remains that would cause a misinvocation.

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?

Only one parameter, whose schema description already covers it at 100%, so the baseline is 3. The description adds provenance by saying the ID is obtained from list_knowledge_bases, which tells the agent how to source a valid value rather than guess.

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 ('Delete an interview knowledge base') and adds scope that separates it from the sibling entry-level delete: 'with all its entries'. An agent can tell it deletes the whole container, not a single question.

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 real usage context: the ID must come from list_knowledge_bases, and the agent must confirm with the user before calling. It does not explicitly contrast with delete_knowledge_base_entry for the single-entry case, which is the one obvious alternative, so it stops short of a 5.

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