Skip to main content
Glama

AceRound AI Interview Copilot

delete_hot_word_library

Destructive

Delete a custom hotword library; roles bound to it are unbound. The ID comes from list_my_hot_words. 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_hot_word_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing the cascade effect (bound roles are unbound), that the action is irreversible, that user confirmation is required beforehand, and the exact auth scope (interviews:write). These are exactly the behavioral facts an agent needs before a destructive call and none are derivable from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences carry the whole definition: the scope/irreversibility constraint is front-loaded ahead of the workflow requirement. 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 destructive tool with no output schema, it covers what gets deleted, the cascade, irreversibility, the confirmation protocol, the ID source, and the auth scope. Only the ID's format/validation is left unstated, a minor gap given the schema's single required field.

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

Parameters3/5

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

Schema description coverage is 0% for the single 'id' parameter, so the description must compensate. It does add provenance ('The ID comes from list_my_hot_words'), which is real value, but it gives no format or validity details for the string itself.

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 a custom hotword library') plus a non-obvious side effect ('roles bound to it are unbound'), which lets an agent distinguish it from create_hot_word_library, update_hot_word_library, and the unrelated delete_* siblings purely by resource name.

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 the precondition for the ID ('comes from list_my_hot_words') and an explicit workflow constraint ('tell the user what will be deleted and get their agreement first'). It does not name an alternative for renaming/removing just the roles, but the when-to-use and confirmation requirement are unambiguous.

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