Skip to main content
Glama

AceRound AI Interview Copilot

delete_knowledge_base_entry

Destructive

Delete one Q&A entry. Entry IDs come from get_knowledge_base. 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_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntry ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the bar is lower, yet the description adds real value: the permanence ("cannot be undone"), the required user sign-in scope, and a mandatory human-confirmation protocol before invocation. These are preconditions and side-effect details annotations cannot express, making the agent substantially less likely to delete irreversibly without consent.

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?

Three compact sentences, front-loaded with the action, then the identifier source, then the irreversible/confirmation warning and the auth requirement in parentheses. Every sentence carries operational content; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter irreversible mutation with no output schema, the definition covers action, identifier provenance, irreversibility, consent protocol, and auth scope. The only gap is what the call returns or how failures surface (e.g. missing/already-deleted ID), which is minor given no output schema exists to describe.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter's schema text is only "Entry ID", so the description's statement that IDs come from get_knowledge_base supplies genuine provenance the schema lacks. That is the one thing an agent actually needs to avoid passing a malformed or guessed identifier.

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 opens with a specific verb+resource: "Delete one Q&A entry." The singular "one Q&A entry" implicitly separates this from the sibling delete_knowledge_base that removes a whole knowledge base, and naming the ID source (get_knowledge_base) further pins down what unit is affected. It stops just short of explicitly naming a sibling for differentiation.

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 clear context for action: retrieve the ID via get_knowledge_base first, tell the user what will be deleted, and get agreement before proceeding. It also states the required auth scope (interviews:write). What's missing is any explicit exclusion — e.g. when to use update or delete_knowledge_base instead — so the boundary 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