Skip to main content
Glama

面灵AI 面试助手

create_hot_word_library

新建一个自建热词库(名称 + 热词列表,单库最多 200 个词,每人最多 20 个库)。返回词库 ID,可用 update_goal_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": {
      "name": "<name>"
    },
    "name": "create_hot_word_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
wordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, closedWorld), it discloses the required authorization scope 'interviews:write' and concrete quotas (200 words per library, 20 libraries per user) — exactly the kind of side-effect context annotations cannot carry. It still omits what happens on quota exhaustion or duplicate names.

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

Conciseness4/5

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

A single dense sentence plus a parenthetical, front-loaded with the action and followed by limits, return value, and permission. Every clause carries information, though the multi-parenthesis structure is slightly dense to parse.

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?

With only two parameters, no output schema, and no nested objects, the definition covers action, quotas, return value, follow-up binding, and auth scope — enough to call it correctly. Missing only edge-case behavior (duplicate names, quota errors) for a full score.

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%, so the description must compensate; it does explain that 'words' is a hot word list and adds a 200-item cap that is absent from the schema. It does not cover the name's 30-character limit, the 50-character per-word limit, or that 'words' is optional and defaults to empty.

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 names a specific verb and resource ('新建一个自建热词库') and specifies the payload (name + hot word list), plus the return value (library ID). It is clearly separable from update/delete/list siblings, though it does not explicitly contrast with generate_hot_words, which could also produce word lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the workflow by saying the returned ID can be bound via update_goal_hot_words, so the agent knows this is the 'create first, bind later' step. However, it never states when not to use this tool or how to choose between creating a custom library and other word-list tools.

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