Skip to main content
Glama

AceRound AI Interview Copilot

update_hot_word_library

Edit a custom hotword library: rename it, replace the word list (words), or add / remove individual words (addWords / removeWords); anything omitted stays unchanged. The ID comes from list_my_hot_words. (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": "update_hot_word_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLibrary ID
nameNo
wordsNo
addWordsNo
removeWordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description adds two valuable facts: partial-update semantics ('anything omitted stays unchanged') and the required auth scope (interviews:write). It stops short of saying whether replacing the whole word list is reversible or what happens on conflicting word operations, so it is strong but not exhaustive.

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?

One dense but well-structured sentence front-loads the edit modes, followed by the partial-update guarantee and the ID/auth notes. Every clause carries distinct information; nothing is redundant with the schema or annotations.

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 5-parameter mutation tool with no output schema, the definition covers purpose, ID sourcing, partial-update behavior, and permissions. The only material omission is how mutually exclusive word-editing parameters behave when combined, which an agent would need to know to avoid surprising overwrites.

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?

With only 20% schema coverage (only id documented), the description compensates well by assigning meaning to name (rename), words (replace the whole list), and addWords/removeWords (incremental edits). It does not address the interaction between words and addWords/removeWords within a single call, nor the length constraints, which is the remaining gap.

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 states a specific verb (edit) and resource (custom hotword library) and then enumerates the concrete edit modes: rename, replace the word list, add/remove individual words. This is enough for an agent to distinguish it from create_hot_word_library and delete_hot_word_library without opening either 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 tells the agent where the required ID comes from (list_my_hot_words) and clarifies that omitted fields stay unchanged, which defines the update context. It does not explicitly say when to prefer this over create/delete or whether words is mutually exclusive with addWords/removeWords, so usage is clear but not fully disambiguated.

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