Skip to main content
Glama

面灵AI 面试助手

generate_hot_words

Read-only

按岗位名称、描述与可选的简历,由 AI 生成一批面试中会说到、语音识别容易认错的专有名词。结果不会自动保存:写入自建词库用 create_hot_word_library / update_hot_word_library,写入岗位自定义热词用 update_goal_hot_words。简历 ID 取自 list_resumes。(需要用户授权,范围 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": {
      "jobName": "<jobName>"
    },
    "name": "generate_hot_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNameYes
resumeIdNo
jobDescriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations it discloses two things the schema does not: the generation result is not auto-saved (consistent with readOnlyHint=true), and the call requires user authorization with the interviews:write scope. It does not characterize the returned payload (size, structure, whether words carry confidence/notes), which matters since there is no output schema; the coexistence of readOnlyHint=true with a write scope is also left unexplained.

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?

Two dense sentences: the capability (with what the generated words actually are) comes first, then non-persistence and the exact follow-up tools, then parameter sourcing and the auth note. Nothing is repeated from structured fields and no sentence is 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 3-parameter generation tool with no output schema and closed-world, read-only annotations, the definition covers purpose, persistence behavior, follow-up actions, parameter sourcing and auth — enough to call it correctly. The only real gap is that the shape of the returned word list is never described.

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 description coverage is 0%, so the description must carry parameter meaning — and it maps all three: job name, job description, and an explicitly optional resume, plus the provenance of resumeId from list_resumes. It still omits constraints an agent would want (maxLength 100/1000 limits, whether jobDescription materially improves output, what happens when resumeId is invalid).

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 gives a specific verb+resource ('由 AI 生成…专有名词') and defines the resource precisely: proper nouns that will come up in interviews and are easily misrecognized by speech recognition, derived from job name, description and an optional resume. This is distinguishable from the sibling save/library tools without opening any schema.

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

Usage Guidelines5/5

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

It explicitly routes the agent: output is not persisted automatically, so writing to a personal word library requires create_hot_word_library / update_hot_word_library, writing to job-specific hot words requires update_goal_hot_words, and the resumeId must be obtained from list_resumes. The when/when-not split between generating and saving is 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