Skip to main content
Glama

面灵AI 面试助手

suggest_hot_word_libraries

Read-only

按岗位名称与描述,由 AI 从官方词库中挑选 2–4 个最匹配的,返回词库 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": {
      "jobName": "<jobName>"
    },
    "name": "suggest_hot_word_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNameYes岗位名称
jobDescriptionNo岗位描述

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotations only establish readOnlyHint=true, destructiveHint=false, openWorldHint=false; the description adds material context beyond that: selection is AI-driven and returns 2–4 items, the result is not persisted, and the call requires user authorization with the interviews:write scope. The non-persistence note is consistent with readOnlyHint=true rather than contradicting it.

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 compact sentences: the first front-loads what is selected and returned, the second carries the persistence caveat, the sibling handoff, and the auth requirement. No sentence is redundant and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the essential return shape (2–4 matches, ID plus name) and the authorization requirement, plus the follow-up tool needed to make the result persist. For a two-parameter read tool with annotations already covering safety, nothing an agent needs to call it correctly is missing.

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 100% and both parameters (jobName, jobDescription) are already documented in the schema, so the description's mention of 'job name and description' adds no syntax or format detail beyond it. Baseline 3 applies since the schema carries the parameter burden.

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 (AI selects 2–4 matching libraries from the official library set for a given job name/description) plus what is returned (library ID and name). It also implicitly distinguishes itself from update_goal_hot_words, which performs the binding step, so an agent can tell the two apart 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?

Explicitly warns that results are not auto-saved and routes the agent to update_goal_hot_words to bind the selection to a job — a clear follow-up condition. It does not name a when-not-to-use condition (e.g. when the user already has libraries bound, or to prefer list_hot_word_libraries for browsing), so it falls short of full 5-level guidance.

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