Skip to main content
Glama

面灵AI 面试助手

update_hot_word_library

修改一个自建热词库:可改名称、整体替换词表(words),或增删个别词(addWords / removeWords);未传的保持原样。词库 ID 取自 list_my_hot_words。(需要用户授权,范围 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
idYes词库 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 discloses the key behavioral traits: fields that are not supplied stay unchanged, and passing words replaces the entire list rather than merging it. It also discloses the required OAuth scope. The description does not say whether replacing words on a library whose words other tools still reference can break anything, which would have made this 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?

A single dense sentence that puts the operation and its modes (the key fact) first and the authorization aside last. Every clause carries 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 description covers purpose, partial-update semantics, ID provenance and auth scope, which is most of what an agent needs before calling it. It omits the return shape and any validation or precedence rules when multiple word parameters are supplied together.

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 only 20% (only id is documented), so the description must compensate — and it does, defining the semantics of all four optional parameters: name is a rename, words is a full replacement, addWords/removeWords are incremental, and omitted fields are left as-is. It does not clarify whether words can coexist with addWords/removeWords, or what happens to duplicates or invalid entries.

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 and resource ("修改一个自建热词库") and enumerates the three supported mutations: rename, replace the whole word list (words), or add/remove individual words (addWords / removeWords). It also points to list_my_hot_words as the source of the ID, which cleanly distinguishes it from the create/delete/list siblings.

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 explains when each parameter mode applies ("可改名称、整体替换词表(words),或增删个别词(addWords / removeWords)") and states that a user authorization scoped to interviews:write is required. It gives no explicit when-not guidance, for example whether words can be combined with addWords/removeWords in the same call.

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